On Tue Sep 26, 2000 at 06:08:20PM +0100, Stephen C. Tweedie wrote:
> Hi,
>
> On Tue, Sep 26, 2000 at 11:02:48AM -0600, Erik Andersen wrote:
>
> > Another approach would be to let user space turn off overcommit.
>
> No. Overcommit only applies to pageable memory. Beancounter is
> really needed for non-pageable resources such as page tables and
> mlock()ed pages.
I think we do agree here, though we are having problems with semantics.
"Overcommit" to me is the same things as Mark Hemment stated earlier in this
thread -- the "fact that the system has over committed its memory resources.
ie. it has sold too many tickets for the number of seats in the plane, and all
the passengers have turned up." Basically any case where too many tickets
have been sold (applied to the entire system, and all subsystems).
To extend the airplane metaphor a bit past credibility...
When an airline sells too many tickets, it bribes people to get off the plane.
For the kernel, it tends to fall over, or starts kicking off pilots and flight
attendants.
If the Beancounter patch lets the kernel count "passengers", classify them
(with user hinting) so the pilot and flight attendants (init, X, or whatever)
always stay on the plane, and has some sane predictable mechanism for booting
non-priveledged passengers, then I am all for it.
How does one provide the kernel with hints as to which processes are sacred?
Where does one find this beancounter patch? How much weight does it add to
the kernel?
-Erik
--
Erik B. Andersen email: [EMAIL PROTECTED]
--This message was written using 73% post-consumer electrons--
-
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/
