netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Dhananjay Phadke <dhananjay.phadke@qlogic.com>
Cc: Jens Rosenboom <me@jayr.de>,
	"netdev\@vger.kernel.org" <netdev@vger.kernel.org>,
	Amit Salecha <amit.salecha@qlogic.com>,
	Ameen Rahman <ameen.rahman@qlogic.com>
Subject: Re: [BUG] netxen: Stops working between 2.6.30 and 2.6.31-rc1
Date: Fri, 20 Nov 2009 09:43:59 -0800	[thread overview]
Message-ID: <m1d43drt0g.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <4B06D234.4060600@qlogic.com> (Dhananjay Phadke's message of "Fri\, 20 Nov 2009 09\:30\:28 -0800")

Dhananjay Phadke <dhananjay.phadke@qlogic.com> writes:

>> Weird. MSI's definitely weren't disabled.  Looking a little farther at
>> your quoted setup MSI work on your board.  This is definitely
>> something specific to the driver.  Except for a few initialization
>> races that are an issue for bonding I am running 2.6.31 just fine.
>
>
> Jens,
>
> Even if /proc/interrupt says PCI-MSI in both cases, single interrupt case is msi
> vs. 4 vector case is msi-x. To confirm that msi-x doesn't work with your
> card/machine, you can still stay on 2.6.31 and set use_msi_x=0 in
> netxen_nic_main.c.
>
> I had tried to make a available a module param to disable msi/msi-x for
> platforms where msi-x doesn't work cleanly, but it was declined by David Miller,
> et al.

MSI-X uses the same messages on the wire is the same as MSI it is
only the programming interface that is different.  So if MSI works and
MSI-X does not it is not a platform problem.

Eric

  reply	other threads:[~2009-11-20 17:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-19 16:39 [BUG] netxen: Stops working between 2.6.30 and 2.6.31-rc1 Jens Rosenboom
2009-11-19 18:07 ` Dhananjay Phadke
2009-11-19 18:36   ` Jens Rosenboom
2009-11-19 22:11     ` Dhananjay Phadke
2009-11-20  7:49       ` Jens Rosenboom
2009-11-20 16:11         ` Jens Rosenboom
2009-11-20  1:19     ` Eric W. Biederman
2009-11-20  7:52       ` Jens Rosenboom
2009-11-20 16:48         ` Eric W. Biederman
2009-11-20 17:30           ` Dhananjay Phadke
2009-11-20 17:43             ` Eric W. Biederman [this message]
2009-11-20 18:07               ` Dhananjay Phadke
2009-11-20 18:21                 ` Eric W. Biederman

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=m1d43drt0g.fsf@fess.ebiederm.org \
    --to=ebiederm@xmission.com \
    --cc=ameen.rahman@qlogic.com \
    --cc=amit.salecha@qlogic.com \
    --cc=dhananjay.phadke@qlogic.com \
    --cc=me@jayr.de \
    --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).