From: Eric Dumazet <eric.dumazet@gmail.com>
To: Ben Hoyt <benhoyt@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Minimizing TCP latency
Date: Mon, 29 Mar 2010 07:34:51 +0200 [thread overview]
Message-ID: <1269840891.2256.28.camel@edumazet-laptop> (raw)
In-Reply-To: <7c93bf1e1003282024p75e70011j31577b42f29cc153@mail.gmail.com>
Le lundi 29 mars 2010 à 16:24 +1300, Ben Hoyt a écrit :
> > I'm happy to receive some pointers via this list [...]
>
> Sorry, I should also have posted more about what I've done in terms of
> reducing latency so far:
>
> * We've already got TCP_NODELAY activated.
One machine sends messages, and messages are not aknowledged by other
part ? Is it one way communication ?
>
> * We've also turned off interrupt coalescing on the network card (for
> example, see http://www.29west.com/docs/THPM/latency-interrupt-coalescing.html).
>
> * We've modified our process's CPU affinity so it runs on a core by
> itself, reducing interrupt-handling latency slightly further.
>
> * Our code is written in C, and we've tried to keep it as close to the
> kernel's socket calls as possible.
>
So we're currently looking further into ways to reduce latency, which
> currently looks like it'll mean digging deeper into the kernel's
> networking options and innards.
>
> FYI, we're using RHE release 4 and kernel version 2.6.9 on x86_64 machines.
What are the targets ? (time constraints)
Mono threaded application handling one tcp flow ?
Are you handling a very light load on few flows, or many flows ?
Are machines all in the same LAN ?
next prev parent reply other threads:[~2010-03-29 5:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 1:29 Minimizing TCP latency Ben Hoyt
2010-03-29 2:43 ` Ben Hoyt
2010-03-29 3:24 ` Ben Hoyt
2010-03-29 5:34 ` Eric Dumazet [this message]
2010-03-30 2:35 ` Ben Hoyt
2010-03-30 4:05 ` Mikael Abrahamsson
2010-03-29 12:40 ` Neil Horman
2010-03-29 15:23 ` Ben Hutchings
2010-03-30 2:36 ` Ben Hoyt
2010-03-30 3:20 ` Ben Hutchings
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=1269840891.2256.28.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=benhoyt@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