All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Chan" <mchan@broadcom.com>
To: "Christoph Lameter" <cl@linux.com>
Cc: "Eric Dumazet" <dada1@cosmosbay.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Network latency regressions from 2.6.22 to 2.6.29
Date: Thu, 16 Apr 2009 14:57:17 -0700	[thread overview]
Message-ID: <1239919037.12883.15.camel@HP1> (raw)
In-Reply-To: <alpine.DEB.1.10.0904161553160.23632@qirst.com>


On Thu, 2009-04-16 at 12:55 -0700, Christoph Lameter wrote:
> On Thu, 16 Apr 2009, Eric Dumazet wrote:
> 
> > Is it a bnx2 or tg3 driver ?
> 
> bnx2.
> 
> > It would be sane to always set on both machines :
> > ethtool -C eth0 rx-usecs 0 rx-frames 1
> > prior to your tests...
> 
> rx-usecs is set to 18 by default by the driver and rx-frames is set to 6.
> We saw some funky behavior with rx-usecs 0 so we left the defaults.

We haven't changed these defaults since the beginning, but firmware
updates between 2.6.22 and 2.6.29 can affect latency.

Yes, Eric is right, using rx-frames 1 will give the best latency number.
(rx-usecs won't matter if rx-frames is set to 1).

> 
> But what does it matter? Just changing the kernel should not cause
> increases in latency.
> 

It will not matter if you use the same out-of-tree driver when switching
kernels.  If you use in-tree driver, the firmware may have changed
between kernel versions.




  reply	other threads:[~2009-04-16 22:03 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
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 [this message]
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=1239919037.12883.15.camel@HP1 \
    --to=mchan@broadcom.com \
    --cc=cl@linux.com \
    --cc=dada1@cosmosbay.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 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.