From: David Miller <davem@davemloft.net>
To: rick.jones2@hp.com
Cc: netdev@vger.kernel.org
Subject: Re: why does tcp_v[46]_conn_request not inc MIB stats
Date: Fri, 14 Sep 2007 20:10:34 -0700 (PDT) [thread overview]
Message-ID: <20070914.201034.38702610.davem@davemloft.net> (raw)
In-Reply-To: <46E5900A.3010009@hp.com>
From: Rick Jones <rick.jones2@hp.com>
Date: Mon, 10 Sep 2007 11:42:18 -0700
> I've been digging around to see about inducing /proc/net/tcp to show
> some "interesting" things for listen sockets (eg backlog depth, its max,
> and dropped connection requests). While there I've noticed that both
> tcp_v[46]_syn_recv_sock and tcp_v[46]conn_request both check that the
> listen queue is full, but only tcp_v[46]_syn_recv_sock increments some
> mib stats for dropped connection requests.
They are checking two different things.
tcp_v{4,6}_conn_request is checking whether we are hitting the limit
for allowing the initial SYN and creating a new embryonic mini-socket.
Exceeding that is not a listen overflow.
tcp_v{4,6}_syn_recv_sock() is processing the end of the 3-way
handshake and wants to create a full established state socket to queue
into the listening parent. This is checking the listening socket
queue limits, and indeed is a listen queue overflow if exceeded.
next prev parent reply other threads:[~2007-09-15 3:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-10 18:42 why does tcp_v[46]_conn_request not inc MIB stats Rick Jones
2007-09-10 21:54 ` Sridhar Samudrala
2007-09-10 22:22 ` Rick Jones
2007-09-15 3:11 ` David Miller
2007-09-18 11:07 ` Andi Kleen
2007-09-18 17:14 ` Rick Jones
2007-09-15 3:10 ` David Miller [this message]
2007-09-17 18:13 ` Rick Jones
2007-09-17 18:26 ` David Miller
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=20070914.201034.38702610.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.com \
/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).