[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160714160803.egrmos7soc6qvrry@f1.synalogic.ca>
Date:	Thu, 14 Jul 2016 09:08:03 -0700
From:	Benjamin Poirier <benjamin.poirier@...il.com>
To:	Matt Wilson <msw@...n.com>
Cc:	Netanel Belgazal <netanel@...apurnalabs.com>,
	David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org, zorik@...apurnalabs.com,
	saeed@...apurnalabs.com, alex@...apurnalabs.com,
	aliguori@...zon.com, ben@...adent.org.uk, romieu@...zoreil.com,
	rami.rosen@...el.com, antoine.tenart@...e-electrons.com,
	"John W. Linville" <linville@...driver.com>
Subject: Re: [PATCH net-next V3] net: ena: Add a driver for Amazon Elastic
 Network Adapters (ENA)
On 2016/07/14 08:22, Matt Wilson wrote:
[...]
> 
> Dave and Benjamin,
> 
> Do you want to see the interrupt moderation extensions to ethtool and
> the sysfs nodes removed before this lands in net-next? Or should
> Netanel remove the sysfs bits until we can extend the ethtool
> interfaces to cover the parameters that ena uses?
I couldn't say what's acceptable or not. A few other drivers (qlcnic,
sfc, ...) already have sysfs tunables. Maybe John, as the new ethtool
maintainer, can weight in too about the changes required to ethtool.
Powered by blists - more mailing lists
 
