From: Andreas Petlund <apetlund@simula.no>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>,
"Eric Dumazet" <eric.dumazet@gmail.com>,
"Arnd Hannemann" <hannemann@nets.rwth-aachen.de>,
LKML <linux-kernel@vger.kernel.org>,
shemminger@vyatta.com, "David Miller" <davem@davemloft.net>,
william.allen.simpson@gmail.com, damian@tvk.rwth-aachen.de
Subject: [net-next PATCH v3 0/3] net: TCP thin-stream latency-improving modifications
Date: Thu, 11 Feb 2010 13:07:05 +0100 [thread overview]
Message-ID: <4B73F2E9.3080306@simula.no> (raw)
This is a series of patches enabling non-intrusive, dynamically triggered modifications that improve retransmission latencies for thin streams.
The patches have been modified according to the feedback from the last round of discussions.
Major changes:
-Possible to disable mechanisms by socket option
-Socket option value boundary check
Cheers,
Andreas Petlund
reply other threads:[~2010-02-11 12:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4B73F2E9.3080306@simula.no \
--to=apetlund@simula.no \
--cc=damian@tvk.rwth-aachen.de \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=hannemann@nets.rwth-aachen.de \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
--cc=william.allen.simpson@gmail.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