This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Update SOMAXCONN value from Linux 5.4
- From: Florian Weimer <fw at deneb dot enyo dot de>
- To: Joseph Myers <joseph at codesourcery dot com>
- Cc: <libc-alpha at sourceware dot org>
- Date: Fri, 29 Nov 2019 09:32:11 +0100
- Subject: Re: Update SOMAXCONN value from Linux 5.4
- References: <alpine.DEB.2.21.1911290110020.9015@digraph.polyomino.org.uk>
* Joseph Myers:
> Linux 5.4 changes the SOMAXCONN value from 128 to 4096 (this isn't in
> a uapi header; various constants related to the kernel/userspace
> interface, including this one, are in the non-uapi linux/socket.h
> header).
>
> This patch increases the value in glibc. As I understand it, it is
> safe to use a higher value even with older kernels (the kernel will
> simply adjust the value passed to listen to be no more than the value
> supported in the kernel), and SOMAXCONN is actually only a default for
> a sysctl value in the kernel that can be changed at runtime. So I
> think updating the value in glibc is a reasonable and safe thing to
> do.
Should we add a deprecation warning to the macro and eventually remove
it, given that it's not actually a constant?