[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <glmbovmv7ahln6omzoas5lrktaafbmxdkbs4mfoummhrlayl7u@s2nv66r7yx43>
Date: Wed, 5 Mar 2025 16:04:08 +0100
From: Michal Koutný <mkoutny@...e.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Christian Brauner <brauner@...nel.org>,
Alexander Mikhalitsyn <alexander@...alicyn.com>, linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-trace-kernel@...r.kernel.org,
Jonathan Corbet <corbet@....net>, Kees Cook <kees@...nel.org>,
"Eric W . Biederman" <ebiederm@...ssion.com>, Oleg Nesterov <oleg@...hat.com>
Subject: Re: [PATCH 2/2] pid: Optional first-fit pid allocation
Hi.
On Fri, Feb 21, 2025 at 04:18:54PM -0800, Andrew Morton <akpm@...ux-foundation.org> wrote:
> This seems thin. Is there more we can tell our users? What are the
> visible effects of this? What are the benefits? Why would they want
> to turn it on?
Thanks for review and comments (also Alexander).
> I mean, there are veritable paragraphs in the changelogs, but just a
> single line in the user-facing docs. Seems there could be more...
I decided not to fiddle with allocation strategies and disable pid_max
in namespaces by default.
Michal
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists