linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: Paul Albrecht <palbrecht@qwest.net>
Cc: linux-kernel@vger.kernel.org, netdev <netdev@oss.sgi.com>
Subject: Re: question about linux tcp request queue handling
Date: Sun, 06 Jul 2003 16:59:30 -0700	[thread overview]
Message-ID: <3F08B7E2.7040208@us.ibm.com> (raw)
In-Reply-To: <001a01c3441c$6fe111a0$6801a8c0@oemcomputer>

Paul Albrecht wrote:

> My server program sets its backlog to one and pauses ninety seconds before
> accepting connections.  Within that ninety second interval, I start three
> client programs that do an active open to my server.  I expect one of
> connections to get discarded when the server's connection backlog limit is
> exceeded.

We actually have two queues - the syn queue and the socket
acccept queue. We move the connection request from the syn
queue to the accept queue of the socket once the 3 way
handshake is complete - i.e. once the state is ESTABLISHED.

If the syn queue is full, requests will get dropped and
the socket will not change state.

When you set a the backlog to 1 in the listen call, what is
being capped is the accept queue. So I would expect your
server to allow only one of those requests in the accept
queue, and the kernel will drop the other two requests.

Actually, details, but we also apply some other conditions
before we actually drop the connection request - we try not to be
so harsh if the syn queue is still fairly empty..

Think thats so, at any rate :).

Nivedita





  reply	other threads:[~2003-07-06 23:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-06 20:24 question about linux tcp request queue handling Nivedita Singhvi
2003-07-07  0:12 ` Paul Albrecht
2003-07-06 23:59   ` Nivedita Singhvi [this message]
2003-07-07  6:20     ` Paul Albrecht
2003-07-07  5:51       ` Nivedita Singhvi
2003-07-07  5:59         ` Nivedita Singhvi
2003-07-07 23:30         ` Paul Albrecht
2003-07-06 21:19 Paul Albrecht
     [not found] <3F08858E.8000907@us.ibm.com.suse.lists.linux.kernel>
     [not found] ` <001a01c3441c$6fe111a0$6801a8c0@oemcomputer.suse.lists.linux.kernel>
     [not found]   ` <3F08B7E2.7040208@us.ibm.com.suse.lists.linux.kernel>
     [not found]     ` <000d01c3444f$e6439600$6801a8c0@oemcomputer.suse.lists.linux.kernel>
     [not found]       ` <3F090A4F.10004@us.ibm.com.suse.lists.linux.kernel>
     [not found]         ` <001401c344df$ccbc63c0$6801a8c0@oemcomputer.suse.lists.linux.kernel>
2003-07-07 21:48           ` Andi Kleen
2003-07-07 22:25             ` Doug McNaught
2003-07-07 23:52               ` Andi Kleen
2003-07-08  0:17                 ` Doug McNaught
2003-07-08  0:25                   ` Andi Kleen
2003-07-08 14:09                   ` Horst von Brand
2003-07-08  4:14             ` Paul Albrecht
2003-07-08 19:23             ` Paul Albrecht

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=3F08B7E2.7040208@us.ibm.com \
    --to=niv@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=palbrecht@qwest.net \
    /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).