From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: netdev@vger.kernel.org
Subject: [Question]: reqsk table size limited to 16?
Date: Fri, 2 Oct 2009 08:11:34 +0200 [thread overview]
Message-ID: <20091002061134.GC5646@gerrit.erg.abdn.ac.uk> (raw)
Can someone please have a look, it may be that I am missing something?
It seems that in the following the maximum number of table entries is set
to always 16, despite sysctl_max_syn_backlog (tcp_max_syn_backlog),
overriding the 'backlog' parameter to listen(2).
net/core/request_sock.c
-----------------------
int reqsk_queue_alloc(struct request_sock_queue *queue,
unsigned int nr_table_entries)
{
size_t lopt_size = sizeof(struct listen_sock);
struct listen_sock *lopt;
nr_table_entries = min_t(u32, nr_table_entries, sysctl_max_syn_backlog);
nr_table_entries = max_t(u32, nr_table_entries, 8);
nr_table_entries = roundup_pow_of_two(nr_table_entries + 1);
//...
for (lopt->max_qlen_log = 3;
(1 << lopt->max_qlen_log) < nr_table_entries;
lopt->max_qlen_log++);
//...
lopt->nr_table_entries = nr_table_entries;
//...
return 0
}
The function is called with an argument 'nr_table_entries', which is then clamped as
sysctl_max_syn_backlog <= nr_table_entries <= 8
If nr_table_entries = 8, then round_pow_of_two(8 + 1) = 16.
The sysctl value is set to a much higher value (default 128 or 1024, net/ipv4/tcp.c).
The reqsk_queue_alloc() gets 'nr_table_entries' passed directly from inet_csk_listen_start(),
which in turn gets its 'nr_table_entries' as the 'backlog' argument to listen(2) via
* net/dccp/proto.c (dccp_listen_start) or
* net/ipv4/af_inet.c (inet_listen).
next reply other threads:[~2009-10-02 6:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 6:11 Gerrit Renker [this message]
2009-10-02 6:25 ` [Question]: reqsk table size limited to 16? Gerrit Renker
2009-10-02 6:50 ` Eric Dumazet
2009-10-02 6:49 ` Eric Dumazet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091002061134.GC5646@gerrit.erg.abdn.ac.uk \
--to=gerrit@erg.abdn.ac.uk \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).