From: Patrick McManus <mcmanus@ducksong.com>
To: Netdev@vger.kernel.org
Subject: RFC [PATCH 0/3] TCP_DEFER_ACCEPT updates
Date: Tue, 26 Feb 2008 20:48:56 -0500 [thread overview]
Message-ID: <1204076936.15970.33.camel@tng> (raw)
Hello,
I have a few patches to try and improve the TCP_DEFER_ACCEPT
implementation. The first two are simple, the third is ante for a
discussion on how this should really be implemented.
Patch 1 : timeout values could not be less than allowed by the max
syn-recv queue size algorithms. This was not simply a matter of rounding
up to the next syn-ack retransmit time, it was enforcing at least 5
retransmits on a non-loaded machine even if the timeout (expressed by
the API in seconds) was set to 1.
Patch 2 : a socket that has completed its handshake but which is waiting
for the first data packet was retransmitting its syn-ack during that
period. This patch suppresses that transmission.
Patch 3 : move the connected (and TCP_DEFER'd) socket to ESTABLISHED
after the handshake, but defer placing it in the accept queue until some
data arrives.
RFC?
-Patrick
next reply other threads:[~2008-02-27 1:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 1:48 Patrick McManus [this message]
2008-03-01 10:41 ` RFC [PATCH 0/3] TCP_DEFER_ACCEPT updates 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=1204076936.15970.33.camel@tng \
--to=mcmanus@ducksong.com \
--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 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.