From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: David Miller <davem@davemloft.net>
Cc: carolyn.wyborny@intel.com, netdev@vger.kernel.org,
gospo@redhat.com, sassmann@redhat.com
Subject: Re: [net 1/8] igb: Update queue reinit function to call dev_close when init of queues fails
Date: Fri, 29 Nov 2013 23:52:26 -0800 [thread overview]
Message-ID: <1385797946.2248.64.camel@jtkirshe-mobl> (raw)
In-Reply-To: <20131129.154757.2160926223289559260.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 1425 bytes --]
On Fri, 2013-11-29 at 15:47 -0500, David Miller wrote:
> From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> Date: Wed, 27 Nov 2013 23:35:55 -0800
>
> > From: Carolyn Wyborny <carolyn.wyborny@intel.com>
> >
> > This patch adds a call to dev_close if the queue reinit fails in order
> > to make clearer to the user that the device is down.
> >
> > Signed-off-by: Carolyn Wyborny <carolyn.wyborny@intel.com>
> > Tested-by: Aaron Brown <aaron.f.brown@intel.com>
> > Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
>
> This is a very bad approach to this problem.
>
> Users absolutely do not expect their entire interface to go down
> simply because an ethtool request cannot be satisfied. This is
> extremely poor quality of implementation.
>
> And in this specific case it absolutely is not necessary.
>
> The only thing that can fail is the queue allocation, so make a
> function which can preserve the previous configuration if the queue
> allocation fails. How about "igb_reinit_interrupt_scheme".
>
> Don't free the q vectors until the very last moment, when you know
> that the allocation of the new q vectors has succeeded.
>
> I'm not applying this patch, it needs to be reimplemented more
> sanely, using the above suggestions or similar.
>
> Thanks.
Thanks for the feedback Dave, I will drop this patch from the series so
that Carolyn can re-work the solution.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-11-30 7:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 7:35 [net 0/8][pull request] Intel Wired LAN Driver Updates Jeff Kirsher
2013-11-28 7:35 ` [net 1/8] igb: Update queue reinit function to call dev_close when init of queues fails Jeff Kirsher
2013-11-29 20:47 ` David Miller
2013-11-30 7:52 ` Jeff Kirsher [this message]
2013-12-02 16:55 ` Wyborny, Carolyn
2013-12-02 17:18 ` Ben Hutchings
2013-12-02 17:39 ` Wyborny, Carolyn
2013-12-02 18:33 ` David Miller
2013-11-28 7:35 ` [net 2/8] igb: Fixed Wake On LAN support Jeff Kirsher
2013-11-28 7:35 ` [net 3/8] e1000: prevent oops when adapter is being closed and reset simultaneously Jeff Kirsher
2013-11-28 7:35 ` [net 4/8] e1000: fix lockdep warning in e1000_reset_task Jeff Kirsher
2013-11-28 7:35 ` [net 5/8] e1000: fix possible reset_task running after adapter down Jeff Kirsher
2013-11-28 7:36 ` [net 6/8] ixgbe: ixgbe_fwd_ring_down needs to be static Jeff Kirsher
2013-11-28 7:36 ` [net 7/8] ixgbe: turn NETIF_F_HW_L2FW_DOFFLOAD off by default Jeff Kirsher
2013-11-28 7:36 ` [net 8/8] ixgbe: Make ixgbe_identify_qsfp_module_generic static Jeff Kirsher
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=1385797946.2248.64.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=carolyn.wyborny@intel.com \
--cc=davem@davemloft.net \
--cc=gospo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=sassmann@redhat.com \
/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).