> > Indeed. But we wont fail the kmalloc with a NULL return > > Isn't that the preferred behaviour, though? If we are completely out > of VM on a no-swap machine, we should be killing one of the existing > processes rather than preventing any progress and keeping all of the > old tasks alive but deadlocked. Unless Im missing something we wont kill any task in that condition - even a SIGKILL will make no odds as everyone is asleep in kmalloc - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- Re: the new VMt Alan Cox
- Re: the new VMt Stephen C. Tweedie
- Re: the new VMt Andrea Arcangeli
- Re: the new VMt Rik van Riel
- Re: the new VMt Andrea Arcangeli
- Re: the new VMt Stephen C. Tweedie
- Re: the new VMt Alan Cox
- Re: the new VMt Stephen C. Tweedie
- Re: the new VMt Alan Cox
- Re: the new VMt Stephen C. Tweedie
- Re: the new VMt Alan Cox
- Re: the new VMt Stephen C. Tweedie
- Re: the new VMt yodaiken
- Re: the new VMt Jamie Lokier
- Re: the new VMt yodaiken
- Re: the new VMt Jamie Lokier
- Re: the new VMt yodaiken
- Re: the new VMt Stephen C. Tweedie
- Re: the new VMt yodaiken
- Re: the new VMt Jamie Lokier
- Re: the new VMt Stephen C. Tweedie