On Sat, Sep 8, 2018 at 11:23 AM Ttttabcd <tttta...@protonmail.com> wrote: > > Thank you very much for your previous answer, sorry for the inconvenience. > > But now I want to ask you one more question. > > The question is why we need two variables to control the syn queue? > > The first is the "backlog" parameter of the "listen" system call that > controls the maximum length limit of the syn queue, it also controls the > accept queue.
By default, and essentially always in practice (AFAIK), Linux installations enable syncookies. With syncookies, there is essentially no limit on the syn queue, or number of incomplete passive connections (as the man page you quoted notes). So in practice the listen() parameter usually controls only the accept queue. > The second is /proc/sys/net/ipv4/tcp_max_syn_backlog, which also controls the > maximum length limit of the syn queue. > > So simply changing one of them and wanting to increase the syn queue is not > working. > > In our last discussion, I understood tcp_max_syn_backlog will retain the last > quarter to the IP that has been proven to be alive That discussion pertains to a code path that is relevant if syncookies are disabled, which is very uncommon (see above). > But if tcp_max_syn_backlog is very large, the syn queue will be filled as > well. > > So I don't understand why not just use a variable to control the syn queue. > > For example, just use tcp_max_syn_backlog, which is the maximum length limit > for the syn queue, and it can also be retained to prove that the IP remains > the last quarter. > > The backlog parameter of the listen system call only controls the accpet > queue. > > I feel this is more reasonable. If I don't look at the source code, I really > can't guess the backlog parameter actually controls the syn queue. > > I always thought that it only controlled the accept queue before I looked at > the source code, because the man page is written like this. Keep in mind that the semantics of the listen() argument and the /proc/sys/net/ipv4/tcp_max_syn_backlog sysctl knob, as described in the man page, are part of the Linux kernel's user-visible API. So, in essence, they cannot be changed. Changing the semantics of system calls and sysctl knobs breaks applications and system configuration scripts. :-) neal
