Re: [patch] cpusets: do not allow TIF_MEMDIE tasks to allocate globally

On Tue, 5 Jun 2007, David Rientjes wrote:

> No, it means that it can allocate anywhere based on the zonelist ordering 
> and then can OOM a very small exclusive cpuset that would never have had 
> any memory pressure if it wasn't violated.

But the alternative is that the exiting process does not save its 
data.

What is this very small exclusive cpuset?


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [patch] cpusets: do not allow TIF_MEMDIE tasks to allocate globally
    • From: David Rientjes <[email protected]>

• References:
  • [patch] cpusets: do not allow TIF_MEMDIE tasks to allocate globally
    • From: David Rientjes <[email protected]>
  • Re: [patch] cpusets: do not allow TIF_MEMDIE tasks to allocate globally
    • From: Paul Jackson <[email protected]>
  • Re: [patch] cpusets: do not allow TIF_MEMDIE tasks to allocate globally
    • From: David Rientjes <[email protected]>

• Prev by Date: Re: [patch] cpusets: do not allow TIF_MEMDIE tasks to allocate globally
• Next by Date: Re: 2.6.22-rc: regression: no irda0 interface (2.6.21 was OK), smsc does not find chip
• Previous by thread: Re: [patch] cpusets: do not allow TIF_MEMDIE tasks to allocate globally
• Next by thread: Re: [patch] cpusets: do not allow TIF_MEMDIE tasks to allocate globally
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]