[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <9BBC4E0CF881AA4299206E2E1412B6264F9CA06C@ORSMSX102.amr.corp.intel.com>
Date: Wed, 30 Oct 2013 20:30:43 +0000
From: "Wyborny, Carolyn" <carolyn.wyborny@...el.com>
To: Ben Hutchings <bhutchings@...arflare.com>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>
CC: "davem@...emloft.net" <davem@...emloft.net>,
Laura Mihaela Vasilescu <laura.vasilescu@...edu.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"gospo@...hat.com" <gospo@...hat.com>,
"sassmann@...hat.com" <sassmann@...hat.com>
Subject: RE: [net-next 9/9] igb: Add ethtool support to configure number of
channels
> -----Original Message-----
> From: netdev-owner@...r.kernel.org [mailto:netdev-owner@...r.kernel.org]
> On Behalf Of Ben Hutchings
> Sent: Tuesday, October 01, 2013 8:59 AM
> To: Kirsher, Jeffrey T
> Cc: davem@...emloft.net; Laura Mihaela Vasilescu; netdev@...r.kernel.org;
> gospo@...hat.com; sassmann@...hat.com
> Subject: Re: [net-next 9/9] igb: Add ethtool support to configure number of
> channels
>
[..]
> In case this fails, is the interface in a consistent state where is it safe to
> reconfigure the interface again or to unbind the driver?
>
> If it fails, and the interface was up, shouldn't it call dev_close() so that it's
> obviously down and the user can then try to bring it up again?
>
> Ben.
Good question. I was delayed in replying as I was giving Laura a chance to reply to this thread.
We call our close routine igb_close(), if the device is up. This does not call dev_close() specifically, however it’s a good suggestion for the error case. I'll update the patch.
Thanks,
Carolyn
Carolyn Wyborny
Linux Development
Networking Division
Intel Corporation
Powered by blists - more mailing lists