From: Eric Dumazet <eric.dumazet@gmail.com>
To: Tom Herbert <therbert@google.com>
Cc: netdev@vger.kernel.org
Subject: Re: Very low latency TCP for clusters
Date: Mon, 19 Jul 2010 19:41:59 +0200 [thread overview]
Message-ID: <1279561319.2553.153.camel@edumazet-laptop> (raw)
In-Reply-To: <AANLkTilNmNZbFWS8LF-UHU65QYIC32HZlgVZ7lXJHxPh@mail.gmail.com>
Le lundi 19 juillet 2010 à 10:05 -0700, Tom Herbert a écrit :
> We have been looking at best case TCP latencies that might be achieved
> within a cluster (low loss fabric). The goal is to have latency
> numbers roughly comparable to that which can be produced using RDMA/IB
> in a low latency configuration (<5 usecs round trip on netperf TCP_RR
> test with one byte data for directly connected hosts as a starting
> point). This would be without changing sockets API, fabric, and
> preferably not using TCP offload or a user space stack.
>
> I think there are at least two techniques that will drive down TCP
> latency: per connection queues and polling queues. Per connection
> queues (supported by device) should eliminate costs of connection
> look-up, hopefully some locking. Polling becomes viable as core
> counts on systems increase, and burning a few CPUs for networking
> polling on behalf of very low-latency threads would be reasonable.
>
> Are there any efforts in progress to integrate per connection queues
> in the stack or integrate polling of queues?
aka "net channel" ;)
What a nightmare...
Anyway, 5 us roundtrip TCP_RR (including user thread work), seems a bit
utopic right now.
Even on loopback
next prev parent reply other threads:[~2010-07-19 17:42 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 [this message]
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
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=1279561319.2553.153.camel@edumazet-laptop \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox