From: Roland Dreier <rdreier@cisco.com>
To: Greg KH <gregkh@suse.de>
Cc: "Kok, Auke" <auke-jan.h.kok@intel.com>,
"Williams, Mitch A" <mitch.a.williams@intel.com>,
linux-kernel@vger.kernel.org, mingo@redhat.com, "Ronciak,
John" <john.ronciak@intel.com>,
"Brandeburg, Jesse" <jesse.brandeburg@intel.com>
Subject: Re: [PATCH 2.6.20.3] Flush writes to MSI-X table
Date: Sat, 24 Mar 2007 19:00:32 -0700 [thread overview]
Message-ID: <adak5x6m69r.fsf@cisco.com> (raw)
In-Reply-To: <20070324234154.GA10057@suse.de> (Greg KH's message of "Sat, 24 Mar 2007 16:41:54 -0700")
> I don't understand your need to try to rush an api change like this in
> so quickly in an area that has a lot of churn and disagreement lately.
> _Especially_ so late in the release cycle, and with no hardware publicly
> availble.
I'm not sure I understood this thread properly, but if I did understand
correctly then this bug affects IRQ balancing on any device with MSI-X
enabled. In which case, there's plenty of publicly available hardware
with MSI-X support (including drivers in the mainline tree for a long
time). A quick grep for pci_enable_msix finds plenty of drivers using
MSI-X now: cciss, ib_mthca, cxgb3, forcedeth, s2io, qla2xxx.
- R.
prev parent reply other threads:[~2007-03-25 2:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 21:08 [PATCH 2.6.20.3] Flush writes to MSI-X table Mitch Williams
2007-03-23 21:07 ` Greg KH
2007-03-23 21:50 ` Kok, Auke
2007-03-23 22:22 ` Greg KH
2007-03-24 0:24 ` Williams, Mitch A
2007-03-24 0:28 ` Greg KH
2007-03-24 0:30 ` Greg KH
2007-03-24 23:33 ` Kok, Auke
2007-03-24 23:41 ` Greg KH
2007-03-25 2:00 ` Roland Dreier [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=adak5x6m69r.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=auke-jan.h.kok@intel.com \
--cc=gregkh@suse.de \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mitch.a.williams@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.