From: David Miller <davem@davemloft.net>
To: christoph.paasch@uclouvain.be
Cc: netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH] tcp: Remove TCPCT
Date: Sun, 17 Mar 2013 14:35:48 -0400 (EDT) [thread overview]
Message-ID: <20130317.143548.1427926053702804045.davem@davemloft.net> (raw)
In-Reply-To: <1363544614-14411-1-git-send-email-christoph.paasch@uclouvain.be>
From: Christoph Paasch <christoph.paasch@uclouvain.be>
Date: Sun, 17 Mar 2013 19:23:34 +0100
> TCPCT uses option-number 253, reserved for experimental use and should
> not be used in production environments.
> Further, TCPCT does not fully implement RFC 6013.
>
> As a nice side-effect, removing TCPCT increases TCP's performance for
> very short flows:
>
> Doing an apache-benchmark with -c 100 -n 100000, sending HTTP-requests
> for files of 1KB size.
>
> before this patch:
> average (among 7 runs) of 20845.5 Requests/Second
> after:
> average (among 7 runs) of 21403.6 Requests/Second
>
> Signed-off-by: Christoph Paasch <christoph.paasch@uclouvain.be>
Applied, thanks Christoph.
prev parent reply other threads:[~2013-03-17 18:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-17 18:23 [PATCH] tcp: Remove TCPCT Christoph Paasch
2013-03-17 18:35 ` David Miller [this message]
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=20130317.143548.1427926053702804045.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=christoph.paasch@uclouvain.be \
--cc=eric.dumazet@gmail.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 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).