linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michael Kerrisk <mtk.manpages@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Manfred Spraul <manfred@colorfullife.com>,
	Davidlohr Bueso <davidlohr@hp.com>,
	KOSAKI Motohiro <kosaki.motohiro@gmail.com>,
	aswin@hp.com, LKML <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	Michael Kerrisk-manpages <mtk.manpages@gmail.com>
Subject: Re: [PATCH] ipc,shm: increase default size for shmmax
Date: Thu, 17 Apr 2014 12:41:18 +0200	[thread overview]
Message-ID: <CAHO5Pa2zguBEpg-S0Zx26qEStF5ZyvrnbU8-sQZfNJEZRMQPqg@mail.gmail.com> (raw)
In-Reply-To: <20140416154631.6d0173498c60619d454ae651@linux-foundation.org>

On Thu, Apr 17, 2014 at 12:46 AM, Andrew Morton
<akpm@linux-foundation.org> wrote:
> On Sun, 13 Apr 2014 20:05:34 +0200 Manfred Spraul <manfred@colorfullife.com> wrote:
>
>> Hi Andrew,
>>
>> On 04/02/2014 12:08 AM, Andrew Morton wrote:
>> > Well, I'm assuming 64GB==infinity. It *was* infinity in the RHEL5
>> > timeframe, but infinity has since become larger so pickanumber.
>>
>> I think infinity is the right solution:
>> The only common case where infinity is wrong would be Android - and
>> Android disables sysv shm entirely.
>>
>> There are two patches:
>> http://marc.info/?l=linux-kernel&m=139730332306185&q=raw
>> http://marc.info/?l=linux-kernel&m=139727299800644&q=raw
>>
>> Could you apply one of them?
>> I wrote the first one, thus I'm biased which one is better.
>
> I like your patch because applying it might encourage you to send more
> kernel patches - I miss the old days ;)
>
> But I do worry about disrupting existing systems so I like Davidlohr's
> idea of making the change a no-op for people who are currently
> explicitly setting shmmax and shmall.

Agreed. It's hard to imagine situations where people might care
nowadays, but there's no limits to people's insane inventiveness. Some
people really might want to set an upper limit.

> In an ideal world, system administrators would review this change,

And in the ideal world, patches such as this would CC
linux-api@vger.kernel.org, as described in
Documentation/SubmitChecklist, so that users who care about getting
advance warning on API changes could be alerted and might even review
and comment...

> would remove their explicit limit-setting and would retest everything
> then roll it out.  But in the real world with Davidlohr's patch, they
> just won't know that we did this and they'll still be manually
> configuring shmmax/shmall ten years from now.  I almost wonder if we
> should drop a printk_once("hey, you don't need to do that any more")
> when shmmax/shmall are altered?

Makes some sense. But then what about the (strange) people who really
do want to set a limit. Do we just say that they have to live with the
message?

Cheers,

Michael

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

  parent reply	other threads:[~2014-04-17 10:41 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 [this message]
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

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=CAHO5Pa2zguBEpg-S0Zx26qEStF5ZyvrnbU8-sQZfNJEZRMQPqg@mail.gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=aswin@hp.com \
    --cc=davidlohr@hp.com \
    --cc=kosaki.motohiro@gmail.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