On Wed, 2007-09-05 at 05:14 -0700, Christoph Lameter wrote:

quoted text
> Using the VM to throttle networking is a pretty bad thing because it=20
> assumes single critical user of memory. There are other consumers of=20
> memory and if you have a load that depends on other things than networkin=
g=20
quoted text
> then you should not kill the other things that want memory.

The VM is a _critical_ user of memory. And I dare say it is the _most_
important user.=20

Every user of memory relies on the VM, and we only get into trouble if
the VM in turn relies on one of these users. Traditionally that has only
been the block layer, and we special cased that using mempools and
PF_MEMALLOC.

Why do you object to me doing a similar thing for networking?

The problem of circular dependancies on and with the VM is rather
limited to kernel IO subsystems, and we only have a limited amount of
them.=20

You talk about something generic, do you mean an approach that is
generic across all these subsystems?

If so, my approach would be it, I can replace mempools as we have them
with the reserve system I introduce.