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

Alan Cox (alan@lxorguk.ukuu.org.uk)
Sun, 6 Aug 2000 19:55:29 +0100 (BST)

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Tigran Aivazian: "Re: bug in blkdev <-> VFS interaction. (oops)"
Previous message: Tigran Aivazian: "bug in blkdev <-> VFS interaction. (oops)"
In reply to: Robert H. de Vries: "Re: can't mlockall() more than 128MB, is this a kernel limitiation ?"
Next in thread: Andi Kleen: "Re: can't mlockall() more than 128MB, is this a kernel limitiation ?"

> >Right now Linux isnt tracking per user resources. You need the beancounter
> >addons to implement per user memory like that
>
> I think Linus has just (test6-pre series) put this facility in the kernel.
> See the new kernel/user.c.

Yep - sort of a toy edition of beancounter. Thats not knocking it -
the full beancounter isnt 2.4 material..

-
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: Tigran Aivazian: "Re: bug in blkdev <-> VFS interaction. (oops)"
Previous message: Tigran Aivazian: "bug in blkdev <-> VFS interaction. (oops)"
In reply to: Robert H. de Vries: "Re: can't mlockall() more than 128MB, is this a kernel limitiation ?"
Next in thread: Andi Kleen: "Re: can't mlockall() more than 128MB, is this a kernel limitiation ?"