OTOH, 2.2.1{3,4} have seen deadlocks because GFP_KERNEL
allocations had eaten up all of memory and a PF_MEMALLOC
allocation couldn't get through. It has also DoSed some
servers where the network driver got temporarily confused
when a GFP_ATOMIC allocation failed.
> > Also killing the low_on_memory will harm performance. You doesn't seems to
> > see what such bit (that should be a per-process thing) is good for.
>
> Also agreed --- removing the per-process flag will just penalise
> _all_ processes when we enter thrashing.
Except that it never was a per-process flag...
(so we didn't lose anything there)
regards,
Rik
-- The Internet is not a network of computers. It is a network of people. That is its real strength.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/