netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: brice@myri.com
Cc: netdev@vger.kernel.org, gallatin@myri.com
Subject: Re: [PATCH net-next] myri10ge: add adaptive coalescing
Date: Tue, 06 Oct 2009 17:25:37 -0700 (PDT)	[thread overview]
Message-ID: <20091006.172537.148962576.davem@davemloft.net> (raw)
In-Reply-To: <4ACB75DB.4060003@myri.com>

From: Brice Goglin <brice@myri.com>
Date: Tue, 06 Oct 2009 18:52:43 +0200

> This patch adds support for adaptive interrupt coalescing to the
> myri10ge driver. It is based on the host periodically look at
> statistics and update the NIC coalescing accordingly.
> 
> The NIC only provides packet throughput and we feel that it is a
> better heuristics than the packet rate heuristics currently used
> in ethtool. Also, assuming that the packet packet rate heuristics
> uses what is actually sent on the wire when using TSO, it would be
> much more expensive to implement correctly, as the driver would
> need to calculate how many packets were sent.
> 
> Signed-off-by: Andrew Gallatin <gallatin@myri.com>
> Signed-off-by: Brice Goglin <brice@myri.com>

Drivers tried to do this as far back as 6 years ago (tg3) and we don't
recommend doing this with NAPI drivers.

You detection code can never respond quick enough in response to
changes in traffic conditions.  By the time you program the new values
into the registers things on the wire can change a lot.

It's also very easy to flap and hit the settings a lot.

That's why we recommend using low hw mitigation settings and simply
leaving it like that.

  reply	other threads:[~2009-10-07  0:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-06 16:52 [PATCH net-next] myri10ge: add adaptive coalescing Brice Goglin
2009-10-07  0:25 ` David Miller [this message]
2009-10-07  1:28   ` Rick Jones
2009-10-07  5:17     ` Brice Goglin
2009-10-07  5:25       ` 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=20091006.172537.148962576.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=brice@myri.com \
    --cc=gallatin@myri.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).