From: Christoph Paasch <christoph.paasch@uclouvain.be>
To: Eric Dumazet <eric.dumazet@gmail.com>, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] tcp: speedup tcp_fixup_rcvbuf()
Date: Thu, 16 May 2013 09:06:20 +0200 [thread overview]
Message-ID: <1697330.SmXeaasf9r@cpaasch-mac> (raw)
In-Reply-To: <1368681955.3301.11.camel@edumazet-glaptop>
Hello Eric,
On Wednesday 15 May 2013 22:25:55 Eric Dumazet wrote:
> tcp_fixup_rcvbuf() contains a loop to estimate initial socket
> rcv space needed for a given mss. With large MTU (like 64K on lo),
> we can loop ~500 times and consume a lot of cpu cycles.
>
> perf top of 200 concurrent netperf -t TCP_CRR
just out of curiosity, how do you run 200 concurrent netperfs?
Is there an option as in iperf (-P) ?
I did not find anything like this in the netperf-code.
Thanks,
Christoph
--
IP Networking Lab --- http://inl.info.ucl.ac.be
MultiPath TCP in the Linux Kernel --- http://multipath-tcp.org
UCLouvain
--
next prev parent reply other threads:[~2013-05-16 7:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 5:25 [PATCH net-next] tcp: speedup tcp_fixup_rcvbuf() Eric Dumazet
2013-05-16 7:06 ` Christoph Paasch [this message]
2013-05-16 7:11 ` Eric Dumazet
2013-05-16 17:42 ` Rick Jones
2013-05-16 15:23 ` Neal Cardwell
2013-05-16 22:20 ` David Miller
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=1697330.SmXeaasf9r@cpaasch-mac \
--to=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).