From: Iliya <vnsavage@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Fwd: per user memory limit and LSM module
Date: Fri, 29 May 2009 16:15:30 +0300 [thread overview]
Message-ID: <b0b0b0000905290615j1a4c1f97q1452bd74d04ec66b@mail.gmail.com> (raw)
In-Reply-To: <b0b0b0000905290611r45b1d528o98ee26ec0f534639@mail.gmail.com>
---------- Forwarded message ----------
From: Iliya <vnsavage@gmail.com>
Date: Fri, May 29, 2009 at 4:11 PM
Subject: Re: per user memory limit and LSM module
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
On Fri, May 29, 2009 at 3:57 PM, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>> Any suggestions on how can I quickly get or maintain a list of all the
>> running tasks per user(or just the memory usage), without patching the
>> kernel would be greatly appreciated.
>
> Even if you could what would you do with it, large parts of memory don't
> have a single owner and even if they did you would have to traverse tens
> of thousands of objects so it would be incredibly slow.
Thank you for your reply.
If I can quickly sum, let's say the tsk->mm->total_vm (although this
would not count the overcommiting) for all tasks owned by a user, I
can limit that.
What I really need is to make sure that none of the users would eat
all the memory or get the system in OOM state.
>
> Take a look at the containers work and OpenVZ as I suspect that is what
> you need to work from.
The containers will probably do the job but the module is
multi-purpose and I would rather have everything at one place if
possible..
>
prev parent reply other threads:[~2009-05-29 13:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 12:51 Iliya
2009-05-29 12:57 ` Alan Cox
[not found] ` <b0b0b0000905290611r45b1d528o98ee26ec0f534639@mail.gmail.com>
2009-05-29 13:15 ` Iliya [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b0b0b0000905290615j1a4c1f97q1452bd74d04ec66b@mail.gmail.com \
--to=vnsavage@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®