Re: can't mlockall() more than 128MB, is this a kernel limitiation ?

Alan Cox (alan@lxorguk.ukuu.org.uk)
Sun, 6 Aug 2000 15:12:52 +0100 (BST)

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Thomas Graichen: "Re: how to actually build SGI's xfs?"
Previous message: Alan Cox: "Re: kernel image (linux vs linux-up)"
In reply to: Robert H. de Vries: "Re: can't mlockall() more than 128MB, is this a kernel limitiation ?"
Next in thread: Robert H. de Vries: "Re: can't mlockall() more than 128MB, is this a kernel limitiation ?"
Reply: Robert H. de Vries: "Re: can't mlockall() more than 128MB, is this a kernel limitiation ?"
Reply: Andi Kleen: "Re: can't mlockall() more than 128MB, is this a kernel limitiation ?"

> IMHO, an ordinary user may only lock a limited amount of memory. Maybe it is
> wise to specify a certain amount which may *not* be locked. This memory is
> reserved for the rest of the processes.

Right now Linux isnt tracking per user resources. You need the beancounter
addons to implement per user memory like that

-
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/

Next message: Thomas Graichen: "Re: how to actually build SGI's xfs?"
Previous message: Alan Cox: "Re: kernel image (linux vs linux-up)"
In reply to: Robert H. de Vries: "Re: can't mlockall() more than 128MB, is this a kernel limitiation ?"
Next in thread: Robert H. de Vries: "Re: can't mlockall() more than 128MB, is this a kernel limitiation ?"
Reply: Robert H. de Vries: "Re: can't mlockall() more than 128MB, is this a kernel limitiation ?"
Reply: Andi Kleen: "Re: can't mlockall() more than 128MB, is this a kernel limitiation ?"