From: Eric W. Biederman > Sent: 19 August 2020 16:01 ... > >> Further the design decisions of pids keeps us densly using pids. So I > >> expect it will be a while before we even come close to using 30 bits of > >> pid space. > > > > Also because it's simply annoying to have to type really large pid > > numbers on the shell. Yes yes, that's a very privileged > > developer-centric complaint but it matters when you have to do a quick > > kill -9. Chromebook users obviously won't care about how large their > > pids are for sure. > > Actually that is one of the reasons (possibly the primary reason) that > we have chosen to keep pid numbers dense. It also helps keep the ps output under 80 cols. > There may be fewer users of unix shells then their used to be, and we > may now have pidfds. But until people stop using pids in shells it is a > very valid reason to keep them densly packed. ISTM that the upper limit should be increased automatically when the number of allocated pids gets large enough that they are likely to run out (or get reused very quickly). Does linux have an O(1) (or do I mean o(1)) pid allocator? Or does it have to do a linear scan to find a gap?? I made the NetBSD pid allocator/lookup use pid_array[pid & mask] then check the high bits matched (incremented on allocate). With a FIFO free list through the unused entries. Fairly easy to double the size and 'unzip' when getting full. And then allocate extra high bits to keep plenty of free values in circulation. David - Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK Registration No: 1397386 (Wales)
Fork