From: Rick Jones <rick.jones2@hp.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Tom Herbert <therbert@google.com>, netdev@vger.kernel.org
Subject: Re: Very low latency TCP for clusters
Date: Tue, 20 Jul 2010 10:24:55 -0700 [thread overview]
Message-ID: <4C45DBE7.8070401@hp.com> (raw)
In-Reply-To: <1279603570.2458.66.camel@edumazet-laptop>
Eric Dumazet wrote:
> Le lundi 19 juillet 2010 à 16:37 -0700, Tom Herbert a écrit :
>
>>That's pretty pokey ;-) I see numbers around 25 usecs between to
>>machines, this is with TCP_NBRR. With TCP_RR it's more like 35 usecs,
>>so eliminating the scheduler is already a big reduction. That leaves
>>18 usecs in device time, interrupt processing, network, and cache
>>misses; 7 usecs in TCP processing, user space. While 5 usecs is an
>>aggressive goal, I am not ready to concede that there's an
>>architectural limit in either NICs, TCP, or sockets that can't be
>>overcome.
>
> Last time I tried TCP_NBRR, it was not working (not even compiled in), I
> guess I should submit a bug report to Rick ;)
Indeed!-) Actually, my first thought upon reading what Tom wrote was "Wow, I'm
amazed it still works" :) That code probably hasn't been visited much since the
heydays of T/TCP (transactional).
Getting it compiled-in probably required a hand-editing of the config.h file
after the ./configure. Patches to add a --enable-nbrr would be graciously accepted.
happy benchmarking,
rick jones
next prev parent reply other threads:[~2010-07-20 17:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-19 17:05 Very low latency TCP for clusters Tom Herbert
2010-07-19 17:35 ` David Miller
2010-07-19 17:41 ` Eric Dumazet
2010-07-19 18:44 ` Tom Herbert
2010-07-19 19:27 ` David Miller
2010-07-19 22:03 ` Eric Dumazet
2010-07-19 23:37 ` Tom Herbert
2010-07-20 5:26 ` Eric Dumazet
2010-07-20 17:24 ` Rick Jones [this message]
2010-07-20 12:57 ` Brian Bloniarz
2010-07-19 18:13 ` Rick Jones
2010-07-19 18:28 ` Nivedita Singhvi
2010-07-19 19:46 ` Mitchell Erblich
2010-07-19 21:16 ` Tom Herbert
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=4C45DBE7.8070401@hp.com \
--to=rick.jones2@hp.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=therbert@google.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.