All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul Albrecht" <palbrecht@qwest.net>
To: "Nivedita Singhvi" <niv@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, "netdev" <netdev@oss.sgi.com>
Subject: Re: question about linux tcp request queue handling
Date: Mon, 7 Jul 2003 16:30:47 -0700	[thread overview]
Message-ID: <001401c344df$ccbc63c0$6801a8c0@oemcomputer> (raw)
In-Reply-To: 3F090A4F.10004@us.ibm.com

Nivedita Singhvi writes:

>
> Again, youre limiting the number of connnection requests
> that are allowed to wait in the *accept* queue, where
> we move to once we're ESTABLISHED.  You arent limiting
> a request sitting in the SYN queue.
>

This statement is inconsistent with the description of this scenario in
Steven's TCP/IP Illustrated.  Specifically, continuing the handshake in the
TCP layer, i.e., sending a syn/ack and moving to the syn_recd state, is
incorrect if the limit of the server's socket backlog would be exceeded.
How do you account for this discrepancy between linux and other
berkeley-derived implementations?



  parent reply	other threads:[~2003-07-07 21:19 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
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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
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='001401c344df$ccbc63c0$6801a8c0@oemcomputer' \
    --to=palbrecht@qwest.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=niv@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.