![]() | |||||||||||
Messages in this thread |
On Sun, Feb 23, 2003 at 10:28:04AM -0700, Eric W. Biederman wrote: > The problem. There is no upper bound to how many rmap > entries there can be at one time. And the unbounded > growth can overwhelm a machine. Eh? By that logic there's no bound to the number of vmas that can exist at a given time. But there is a bound on the number that a single process can force the system into using, and that limit also caps the number of rmap entries the process can bring into existance. Virtual address space is not free, and there are already mechanisms in place to limit it which, given that the number of rmap entries are directly proportion to the amount of virtual address space in use, probably need proper configuration. > The goal is to provide an overall system cap on the number > of rmap entries. No, the goal is to have a stable system under a variety of workloads that performs well. User exploitable worst case behaviour is a bad idea. Hybrid solves that at the expense of added complexity. -ben -- Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||
| Last update: 2005-03-22 13:33 [from the cache] ©2003-2008 | |||||||||||