From: Andrew Morton <akpm@linux-foundation.org>
To: Davidlohr Bueso <davidlohr@hp.com>
Cc: Manfred Spraul <manfred@colorfullife.com>,
aswin@hp.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] ipc,shm: increase default size for shmmax
Date: Tue, 1 Apr 2014 12:26:23 -0700 [thread overview]
Message-ID: <20140401122623.30f9d4e8106031f714e01ebb@linux-foundation.org> (raw)
In-Reply-To: <1396371699.25314.11.camel@buesod1.americas.hpqcorp.net>
On Tue, 01 Apr 2014 10:01:39 -0700 Davidlohr Bueso <davidlohr@hp.com> wrote:
> > > EINVAL A new segment was to be created and size < SHMMIN or size >
> > > SHMMAX, or no new segment was to be created, a segment with given key
> > > existed, but size is greater than the size of that segment.
> >
> > So their system will act as if they had set SHMMAX=enormous. What
> > problems could that cause?
>
> So, just like any sysctl configurable, only privileged users can change
> this value. If we remove this option, users can theoretically create
> huge segments, thus ignoring any custom limit previously set. This is
> what I fear.
What's wrong with that? Waht are we actually ptoecting the system
from? tmpfs exhaustion?
> Think of it kind of like mlock's rlimit. And for that
> matter, why does sysctl exist at all, the same would go for the rest of
> the limits.
These things exist to protect the system from intentional or accidental
service denials. What are the service denials in this case?
> > Look. The 32M thing is causing problems. Arbitrarily increasing the
> > arbitrary 32M to an arbitrary 128M won't fix anything - we still have
> > the problem. Think bigger, please: how can we make this problem go
> > away for ever?
>
> That's the thing, I don't think we can make it go away without breaking
> userspace.
Still waiting for details!
> I'm not saying that my 4x increase is the correct value, I
> don't think any default value is really correct, as with any other
> hardcoded limits there are pros and cons. That's really why we give
> users the option to change it to the "correct" one via sysctl. All I'm
> saying is that 32mb is just too small for default in today's systems,
> and increasing it is just making a bad situation a tiny bit better.
Let's understand what's preventing us from making it a great deal better.
--
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>
prev parent reply other threads:[~2014-04-01 19:26 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 3:06 Davidlohr Bueso
2014-03-31 21:32 ` Andrew Morton
2014-03-31 22:59 ` Davidlohr Bueso
2014-03-31 23:13 ` Andrew Morton
2014-03-31 23:25 ` Davidlohr Bueso
2014-04-01 0:05 ` Andrew Morton
2014-04-01 6:29 ` Kamezawa Hiroyuki
2014-04-01 19:19 ` Andrew Morton
2014-04-01 20:15 ` KOSAKI Motohiro
2014-04-01 20:26 ` Davidlohr Bueso
2014-04-02 0:11 ` Kamezawa Hiroyuki
2014-04-02 1:02 ` Kamezawa Hiroyuki
2014-04-02 14:55 ` One Thousand Gnomes
2014-04-02 23:47 ` Kamezawa Hiroyuki
2014-04-01 17:01 ` Davidlohr Bueso
2014-04-01 18:10 ` KOSAKI Motohiro
2014-04-01 18:31 ` Davidlohr Bueso
2014-04-01 19:51 ` KOSAKI Motohiro
2014-04-01 21:01 ` Davidlohr Bueso
2014-04-01 21:12 ` KOSAKI Motohiro
2014-04-01 21:29 ` Andrew Morton
2014-04-01 21:41 ` KOSAKI Motohiro
2014-04-01 21:48 ` Andrew Morton
2014-04-01 22:02 ` Davidlohr Bueso
2014-04-01 22:08 ` Andrew Morton
2014-04-13 18:05 ` Manfred Spraul
2014-04-13 23:15 ` Davidlohr Bueso
2014-04-16 22:46 ` Andrew Morton
2014-04-16 23:19 ` Davidlohr Bueso
2014-04-17 10:41 ` Michael Kerrisk
2014-04-17 16:41 ` Manfred Spraul
2014-04-17 20:19 ` Michael Kerrisk (man-pages)
2014-04-01 22:49 ` KOSAKI Motohiro
2014-04-01 23:28 ` Davidlohr Bueso
2014-04-01 23:56 ` KOSAKI Motohiro
2014-04-02 0:40 ` Davidlohr Bueso
2014-04-02 1:08 ` Greg Thelen
2014-04-02 1:58 ` Kamezawa Hiroyuki
2014-04-02 2:11 ` Greg Thelen
2014-04-03 0:20 ` [PATCH] ipc,shm: disable shmmax and shmall by default Davidlohr Bueso
2014-04-03 14:07 ` Kamezawa Hiroyuki
2014-04-03 19:02 ` Manfred Spraul
2014-04-03 19:50 ` Davidlohr Bueso
2014-04-03 23:39 ` KOSAKI Motohiro
2014-04-04 5:00 ` Davidlohr Bueso
2014-04-05 18:24 ` KOSAKI Motohiro
2014-04-06 6:42 ` Manfred Spraul
2014-04-06 16:54 ` Davidlohr Bueso
2014-04-03 22:29 ` KOSAKI Motohiro
2014-04-03 23:47 ` KOSAKI Motohiro
2014-04-11 18:28 ` Manfred Spraul
2014-04-11 20:27 ` Davidlohr Bueso
2014-04-11 20:48 ` Davidlohr Bueso
2014-04-12 8:50 ` Manfred Spraul
2014-04-12 15:33 ` Davidlohr Bueso
2014-04-01 21:43 ` [PATCH] ipc,shm: increase default size for shmmax Davidlohr Bueso
2014-04-01 19:26 ` Andrew Morton [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=20140401122623.30f9d4e8106031f714e01ebb@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aswin@hp.com \
--cc=davidlohr@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=manfred@colorfullife.com \
/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