Andrew Morton wrote:
Daniel Phillips <[EMAIL PROTECTED]> wrote:
What happened to the case where we just fill memory full of dirty file
pages backed by a remote disk?
Processes which are dirtying those pages throttle at
/proc/sys/vm/dirty_ratio% of memory dirty. So it is not possible to "fill"
memory with dirty pages. If the amount of physical memory which is dirty
exceeds 40%: bug.
Hi Andrew,
So we make 400 MB of a 1 GB system unavailable for write caching just to
get around the network receive starvation issue?
What happens if some in kernel user grabs 68% of kernel memory to do some
very important thing, does this starvation avoidance scheme still work?
Regards,
Daniel
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
