[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1317167146.2845.48.camel@bwh-desktop>
Date: Wed, 28 Sep 2011 00:45:46 +0100
From: Ben Hutchings <bhutchings@...arflare.com>
To: Neil Horman <nhorman@...driver.com>
Cc: Andy Gospodarek <andy@...yhouse.net>,
Stephen Hemminger <stephen.hemminger@...tta.com>,
jeffrey t kirsher <jeffrey.t.kirsher@...el.com>,
David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
gospo@...hat.com, Alexander H Duyck <alexander.h.duyck@...el.com>
Subject: Re: [net-next 11/13] igb: Make Tx budget for NAPI user adjustable
On Tue, 2011-09-20 at 16:23 -0400, Neil Horman wrote:
[...]
> This is the work Andy is referring to for those interested:
> http://marc.info/?l=linux-kernel&m=131644727521409&w=2
>
> This version has Gregs Ack, and is waiting for an Ack from Jesse Barnes at the
> moment.
While I think it's useful to be able to list all IRQs assigned to a PCI
device, this doesn't tell us anything about the way they're associated
with queues.
> I think Andy's probably right, theres room here for expansion to create
> a relationship between a given interrupt and a napi wieght. I expect what would
> be most direct would be adding a napi_weight attribute that was conditional on
> the class of the pci device allocating the irqs (make it visible for class 0x200
> devs, invisible for others).
That's a terrible idea; what has NAPI got to do with PCI devices?
Ben.
--
Ben Hutchings, Staff 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.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists