netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Hutchings <bhutchings@solarflare.com>
To: Christoph Lameter <cl@linux.com>
Cc: netdev@vger.kernel.org
Subject: Re: Network latency regressions from 2.6.22 to 2.6.29
Date: Thu, 16 Apr 2009 19:07:59 +0100	[thread overview]
Message-ID: <1239905279.3203.30.camel@achroite> (raw)
In-Reply-To: <alpine.DEB.1.10.0904161151330.13531@qirst.com>

On Thu, 2009-04-16 at 12:10 -0400, Christoph Lameter wrote:
> The following are results of lantency measurements using udpping
> (available from http://gentwo.org/ll). It shows that significant latencies
> were added since 2.6.27. I surely wish we could get back to times below 90
> microseconds.
[...]

This "90 microseconds" figure is specific to a particular driver and
hardware.  Have you verified that it applies to others?  The variation
you've reported is tiny compared to the improvements that can be made or
lost by hardware tuning.

Ben.

-- 
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.


  parent reply	other threads:[~2009-04-16 18:08 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-16 16:10 Network latency regressions from 2.6.22 to 2.6.29 Christoph Lameter
2009-04-16 17:21 ` Rick Jones
2009-04-16 19:06   ` Christoph Lameter
2009-04-16 19:29     ` Eric Dumazet
2009-04-16 19:33       ` Christoph Lameter
2009-04-16 22:47         ` David Miller
2009-04-17 13:46           ` Christoph Lameter
2009-04-17 21:43             ` Ilpo Järvinen
2009-04-16 20:05     ` Rick Jones
2009-04-16 18:07 ` Ben Hutchings [this message]
2009-04-16 19:02   ` Christoph Lameter
2009-04-16 21:19     ` Ben Hutchings
2009-04-16 22:47     ` David Miller
2009-04-16 19:43 ` Eric Dumazet
2009-04-16 19:50   ` Eric Dumazet
2009-04-16 20:01     ` Christoph Lameter
2009-04-16 23:00       ` David Miller
2009-04-17 16:42         ` Network latency regressions from 2.6.22 to 2.6.29 (results with IRQ affinity) Christoph Lameter
2009-04-18  8:18           ` Eric Dumazet
2009-04-18  8:20             ` Eric Dumazet
2009-04-18 19:43           ` Eric Dumazet
2009-04-20 17:29             ` Christoph Lameter
2009-04-20 17:57               ` Eric Dumazet
2009-04-20 18:13                 ` Christoph Lameter
2009-04-20 18:46                   ` Eric Dumazet
2009-04-20 19:16                     ` Christoph Lameter
2009-04-20 20:07                       ` Eric Dumazet
2009-04-20 21:14                         ` Christoph Lameter
2009-04-20 21:52                           ` Eric Dumazet
2009-04-21 14:00                             ` Christoph Lameter
2009-04-21 19:36                             ` Network latency regressions from 2.6.22 to 2.6.29 (MSI off) Christoph Lameter
2009-04-20 19:44               ` Network latency regressions from 2.6.22 to 2.6.29 (results with IRQ affinity) Evgeniy Polyakov
2009-04-16 19:55   ` Network latency regressions from 2.6.22 to 2.6.29 Christoph Lameter
2009-04-16 21:57     ` Michael Chan
2009-04-17 13:47       ` Christoph Lameter
2009-04-16 22:59     ` 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=1239905279.3203.30.camel@achroite \
    --to=bhutchings@solarflare.com \
    --cc=cl@linux.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).