netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Hutchings <bhutchings@solarflare.com>
To: "Wyborny, Carolyn" <carolyn.wyborny@intel.com>
Cc: David Miller <davem@davemloft.net>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: RE: [RFC 2/2] ethtool: Add support for DMA Coalescing feature config to ethtool.
Date: Thu, 30 Jun 2011 19:06:19 +0100	[thread overview]
Message-ID: <1309457179.2701.6.camel@bwh-desktop> (raw)
In-Reply-To: <EDC0E76513226749BFBC9C3FB031318F016F8D2A76@orsmsx508.amr.corp.intel.com>

On Thu, 2011-06-30 at 10:52 -0700, Wyborny, Carolyn wrote:
[...]
> >You may wish to propose a new command structure that covers both IRQ and
> >DMA moderation.  They seem to be related, since DMA cannot be delayed
> >longer than the corresponding IRQ.  We are currently lacking a way to
> >specify different IRQ moderation for multiqueue devices where the queues
> >are not all used in the same way.
> >
> >Ben.
> >
> >--
> >Ben Hutchings, Senior Software Engineer, Solarflare
> >Not speaking for my employer; that's the marketing department's job.
> >They asked us to note that Solarflare product names are trademarked.
> 
> I will try to do this.  Confirming you are suggesting a replacement or
> an alternate for the current -c/-C coalesce settings with perhaps some
> room reserved for some future coalescing type features and enable
> settings per queue?
[...]

Yes.  I'm not insisting that you must do this instead of just defining
the operations for DMA coalescing, but it would be helpful.

Ben.

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


      reply	other threads:[~2011-06-30 18:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-14 17:13 [RFC 2/2] ethtool: Add support for DMA Coalescing feature config to ethtool Carolyn Wyborny
2011-06-14 18:51 ` Ben Hutchings
2011-06-14 20:19   ` Wyborny, Carolyn
2011-06-16 23:53     ` Ben Hutchings
2011-06-17  3:33 ` David Miller
2011-06-17 15:50   ` Wyborny, Carolyn
2011-06-17 18:54     ` David Miller
2011-06-21 17:23       ` Wyborny, Carolyn
2011-06-21 17:38         ` Ben Hutchings
2011-06-30 17:52           ` Wyborny, Carolyn
2011-06-30 18:06             ` Ben Hutchings [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=1309457179.2701.6.camel@bwh-desktop \
    --to=bhutchings@solarflare.com \
    --cc=carolyn.wyborny@intel.com \
    --cc=davem@davemloft.net \
    --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).