On Mon, Mar 02, 2015 at 08:13:23AM -0500, Austin S Hemmelgarn wrote: > If 16-bit PID's aren't a concern anymore, then why do we still default to > treating it like a 16-bit signed int (the default for > /proc/sys/kernel/pid_max is 32768)?
Inertia. It has to start there for backward compatibility. Now it's trivial to adjust dynamically and majority of the users don't need to worry about it, so there's no pressing reason to bump it up by default. 16bit pid_t was already a dying breed on 32bit config and it never was an option on 64bit. Any remotely modern distros in the past decade, whether 32 or 64bit, wouldn't have any problem with it. The only possibly problematic case would be legacy code which for some reason explicitly used 16bit integer types instead of pid_t, but at this point, we shouldn't be basing any design decisions on that. If anybody is still depending on that, there are different ways ton deal with the issue on their end including namespacing its pid space. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
