From: Francois - kml <fckernml@free.fr>
To: linux-mm@kvack.org
Subject: Migrating SYSV Limits to rlimit ?
Date: Tue, 31 Mar 2009 22:44:13 +0200 [thread overview]
Message-ID: <200903312244.13687.fckernml@free.fr> (raw)
Hi,
Most distros sets their own shmmax/shmall values.
DB admins wants and usually sets large values for their processes.
Global limits means there's no guarantee, except the upper limit.
So I'm currently working on a patch moving sysv shm limits to rlimit, which
would allow a finer grained tuning. Currently:
- Lower by default shmmax/shmall values (at least the mainline ones)
- Allow raising those limits through sysctl, privilegied /proc access or
setrlimit w/CAP_SYS_RESOURCE
- Limit resources by user with the user accounting struct
- Set the initial values through Kconfig
- Bind of sysctl modifications to init's rlimit hard values
I'm looking for comments.
Is that something that could interest a specific branch ?
Refs: Bugzilla Bug 11381
Some discussion about it:
http://marc.info/?t=112315565600001&r=1&w=2
Francois
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
reply other threads:[~2009-03-31 20:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200903312244.13687.fckernml@free.fr \
--to=fckernml@free.fr \
--cc=linux-mm@kvack.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