From: David Miller <davem@davemloft.net>
To: mchan@broadcom.com
Cc: netdev@vger.kernel.org, gospo@redhat.com, jfeeney@redhat.com
Subject: Re: [PATCH 1/3] bnx2: Fix lost MSI-X problem on 5709 NICs.
Date: Tue, 27 Apr 2010 14:38:25 -0700 (PDT) [thread overview]
Message-ID: <20100427.143825.216754145.davem@davemloft.net> (raw)
In-Reply-To: <1272403691-2934-1-git-send-email-mchan@broadcom.com>
From: "Michael Chan" <mchan@broadcom.com>
Date: Tue, 27 Apr 2010 14:28:09 -0700
> It has been reported that under certain heavy traffic conditions in MSI-X
> mode, the driver can lose an MSI-X vector causing all packets in the
> associated rx/tx ring pair to be dropped. The problem is caused by
> the chip dropping the write to unmask the MSI-X vector by the kernel
> (when migrating the IRQ for example).
>
> This can be prevented by increasing the GRC timeout value for these
> register read and write operations.
>
> Thanks to Dell for helping us debug this problem.
>
> Signed-off-by: Michael Chan <mchan@broadcom.com>
Applied to net-2.6
prev parent reply other threads:[~2010-04-27 21:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 21:28 [PATCH 1/3] bnx2: Fix lost MSI-X problem on 5709 NICs Michael Chan
2010-04-27 21:28 ` [PATCH 2/3] bnx2: Prevent "scheduling while atomic" warning with cnic, bonding and vlan Michael Chan
2010-04-27 21:28 ` [PATCH 3/3] bnx2: Update version to 2.0.9 Michael Chan
2010-04-27 21:38 ` David Miller
2010-04-27 21:38 ` [PATCH 2/3] bnx2: Prevent "scheduling while atomic" warning with cnic, bonding and vlan David Miller
2010-04-27 21:38 ` David Miller [this message]
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=20100427.143825.216754145.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=gospo@redhat.com \
--cc=jfeeney@redhat.com \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
/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).