Thread (12 messages) 12 messages, 6 authors, 2025-03-10

Re: [PATCH 2/2] pid: Optional first-fit pid allocation

From: Andrew Morton <akpm@linux-foundation.org>
Date: 2025-02-22 00:18:55
Also in: linux-fsdevel, linux-trace-kernel, lkml

On Fri, 21 Feb 2025 18:02:49 +0100 Michal Koutný [off-list ref] wrote:
quoted hunk ↗ jump to hunk
--- a/Documentation/admin-guide/sysctl/kernel.rst
+++ b/Documentation/admin-guide/sysctl/kernel.rst
@@ -1043,6 +1043,8 @@ The last pid allocated in the current (the one task using this sysctl
 lives in) pid namespace. When selecting a pid for a next task on fork
 kernel tries to allocate a number starting from this one.
 
+When set to -1, first-fit pid numbering is used instead of the next-fit.
+
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?

I mean, there are veritable paragraphs in the changelogs, but just a
single line in the user-facing docs.  Seems there could be more...
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help