From: yzhu1 <Yanjun.Zhu@windriver.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>, <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <gospo@redhat.com>, <sassmann@redhat.com>
Subject: Re: [net v2 2/7] e1000: prevent oops when adapter is being closed and reset simultaneously
Date: Mon, 2 Dec 2013 17:50:06 +0800 [thread overview]
Message-ID: <529C57CE.1040801@windriver.com> (raw)
In-Reply-To: <529A145C.4030503@cogentembedded.com>
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
On 12/01/2013 12:37 AM, Sergei Shtylyov wrote:
> Hello.
>
> On 30-11-2013 13:20, Jeff Kirsher wrote:
>
>> From: yzhu1 <yanjun.zhu@windriver.com>
>
>> This change is based on a similar change made to e1000e support in
>> commit bb9e44d0d0f4 ("e1000e: prevent oops when adapter is being closed
>> and reset simultaneously"). The same issue has also been observed
>> on the older e1000 cards.
>
>> Here, we have increased the RESET_COUNT value to 50 because there are
>> too
>> many accesses to e1000 nic on stress tests to e1000 nic, it is not
>> enough
>> to set RESET_COUT 25. Experimentation has shown that it is enough to set
>> RESET_COUNT 50.
>
>> Signed-off-by: yzhu1 <yanjun.zhu@windriver.com>
>
> Jeff, why are you accepting patches without real name in the
> sign-off line?
>
>> Tested-by: Aaron Brown <aaron.f.brown@intel.com>
>> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
>
> WBR, Sergei
>
>
Hi,
Thanks for the advice from Sergei. I made a new patch with the name
"yanjun.zhu".
Best Regards!
Zhu Yanjun
[-- Attachment #2: 0001-e1000-prevent-oops-when-adapter-is-being-closed-and-.patch --]
[-- Type: text/x-patch, Size: 2468 bytes --]
>From 54e9e48a9f878eb45f0cc6322415244d7a9f1598 Mon Sep 17 00:00:00 2001
From: yzhu1 <yanjun.zhu@windriver.com>
Date: Fri, 22 Nov 2013 15:46:48 +0800
Subject: [PATCH 1/1] e1000: prevent oops when adapter is being closed and
reset simultaneously
This change is based on a similar change made to e1000e support in
commit bb9e44d0d0f4 ("e1000e: prevent oops when adapter is being closed
and reset simultaneously"). The same issue has also been observed
on the older e1000 cards.
Here, we have increased the RESET_COUNT value to 50 because there are too
many accesses to e1000 nic on stress tests to e1000 nic, it is not enough
to set RESET_COUT 25. Experimentation has shown that it is enough to set
RESET_COUNT 50.
Signed-off-by: yanjun.zhu <yanjun.zhu@windriver.com>
---
drivers/net/ethernet/intel/e1000/e1000.h | 5 +++++
drivers/net/ethernet/intel/e1000/e1000_main.c | 9 +++++++++
2 files changed, 14 insertions(+)
diff --git a/drivers/net/ethernet/intel/e1000/e1000.h b/drivers/net/ethernet/intel/e1000/e1000.h
index 58c1472..0af4a8e 100644
--- a/drivers/net/ethernet/intel/e1000/e1000.h
+++ b/drivers/net/ethernet/intel/e1000/e1000.h
@@ -83,6 +83,11 @@ struct e1000_adapter;
#define E1000_MAX_INTR 10
+/*
+ * Count for polling __E1000_RESET condition every 10-20msec.
+ */
+#define E1000_CHECK_RESET_COUNT 50
+
/* TX/RX descriptor defines */
#define E1000_DEFAULT_TXD 256
#define E1000_MAX_TXD 256
diff --git a/drivers/net/ethernet/intel/e1000/e1000_main.c b/drivers/net/ethernet/intel/e1000/e1000_main.c
index e386228..c0f5217 100644
--- a/drivers/net/ethernet/intel/e1000/e1000_main.c
+++ b/drivers/net/ethernet/intel/e1000/e1000_main.c
@@ -1440,6 +1440,10 @@ static int e1000_close(struct net_device *netdev)
{
struct e1000_adapter *adapter = netdev_priv(netdev);
struct e1000_hw *hw = &adapter->hw;
+ int count = E1000_CHECK_RESET_COUNT;
+
+ while (test_bit(__E1000_RESETTING, &adapter->flags) && count--)
+ usleep_range(10000, 20000);
WARN_ON(test_bit(__E1000_RESETTING, &adapter->flags));
e1000_down(adapter);
@@ -4963,6 +4967,11 @@ static int __e1000_shutdown(struct pci_dev *pdev, bool *enable_wake)
netif_device_detach(netdev);
if (netif_running(netdev)) {
+ int count = E1000_CHECK_RESET_COUNT;
+
+ while (test_bit(__E1000_RESETTING, &adapter->flags) && count--)
+ usleep_range(10000, 20000);
+
WARN_ON(test_bit(__E1000_RESETTING, &adapter->flags));
e1000_down(adapter);
}
--
1.7.9.5
next prev parent reply other threads:[~2013-12-02 9:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-30 9:20 [net v2 0/7][pull request] Intel Wired LAN Driver Updates Jeff Kirsher
2013-11-30 9:20 ` [net v2 1/7] igb: Fixed Wake On LAN support Jeff Kirsher
2013-11-30 9:20 ` [net v2 2/7] e1000: prevent oops when adapter is being closed and reset simultaneously Jeff Kirsher
2013-11-30 16:37 ` Sergei Shtylyov
2013-12-02 9:50 ` yzhu1 [this message]
2013-12-02 16:12 ` David Miller
2013-12-03 2:02 ` yzhu1
2013-12-03 2:22 ` Jeff Kirsher
2013-12-03 2:25 ` yzhu1
2013-12-03 5:26 ` David Miller
2013-11-30 9:20 ` [net v2 3/7] e1000: fix lockdep warning in e1000_reset_task Jeff Kirsher
2013-11-30 9:20 ` [net v2 4/7] e1000: fix possible reset_task running after adapter down Jeff Kirsher
2013-11-30 9:20 ` [net v2 5/7] ixgbe: ixgbe_fwd_ring_down needs to be static Jeff Kirsher
2013-11-30 9:20 ` [net v2 6/7] ixgbe: turn NETIF_F_HW_L2FW_DOFFLOAD off by default Jeff Kirsher
2013-11-30 9:20 ` [net v2 7/7] ixgbe: Make ixgbe_identify_qsfp_module_generic static Jeff Kirsher
2013-11-30 17:46 ` [net v2 0/7][pull request] Intel Wired LAN Driver Updates David Miller
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=529C57CE.1040801@windriver.com \
--to=yanjun.zhu@windriver.com \
--cc=davem@davemloft.net \
--cc=gospo@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
--cc=sassmann@redhat.com \
--cc=sergei.shtylyov@cogentembedded.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).