[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160714161511.GA30697@u54ee753d2d1854bda401.ant.amazon.com>
Date: Thu, 14 Jul 2016 09:15:11 -0700
From: Matt Wilson <msw@...n.com>
To: Benjamin Poirier <benjamin.poirier@...il.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 Thu, Jul 14, 2016 at 09:08:03AM -0700, Benjamin Poirier wrote:
> 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.
We definitely want ethtool to handle all the settings, it's just a
question of when. We also want to address and resolve all the great
feedback so far, and since you originally raised the point about
extending ethtool I wanted to see if you have any major objection.
--msw
Powered by blists - more mailing lists