netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: Brice.Goglin@ens-lyon.org, bgoglin@free.fr
Cc: rick.jones2@hp.com, brice@myri.com, netdev@vger.kernel.org,
	gallatin@myri.com
Subject: Re: [PATCH net-next] myri10ge: add adaptive coalescing
Date: Tue, 06 Oct 2009 22:25:21 -0700 (PDT)	[thread overview]
Message-ID: <20091006.222521.167077213.davem@davemloft.net> (raw)
In-Reply-To: <4ACC247A.9020504@free.fr>

From: Brice Goglin <bgoglin@free.fr>
Date: Wed, 07 Oct 2009 07:17:46 +0200

> Rick Jones wrote:
>> David Miller wrote:
>>> 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.
>>
>> Doesn't e1000(e) still try to do adaptive coalescing?
> 
> mlx_en, benet, sfc, ... do as well.

If the patches that added that code slipped by me, my bad.  But
if I had noticed I would have been against them as well.

It really isn't the right thing to do.  By the same arguments
it is even arguable to turn off TCP congestion control completely
on local subnets.

It is absolutely impossible to react to on-the-wire changes in
traffic patterns at the granularity in which we get to execute.
It simply is not possible to do it right.

      reply	other threads:[~2009-10-07  5: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
2009-10-07  1:28   ` Rick Jones
2009-10-07  5:17     ` Brice Goglin
2009-10-07  5:25       ` David Miller [this message]

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.222521.167077213.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=Brice.Goglin@ens-lyon.org \
    --cc=bgoglin@free.fr \
    --cc=brice@myri.com \
    --cc=gallatin@myri.com \
    --cc=netdev@vger.kernel.org \
    --cc=rick.jones2@hp.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;
as well as URLs for NNTP newsgroup(s).