From: Avi Kivity <avi@redhat.com>
To: michael@ellerman.id.au
Cc: Matthew Wilcox <matthew@wil.cx>,
Sheng Yang <sheng@linux.intel.com>,
kvm@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
jbarnes@virtuousgeek.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, Matthew Wilcox <willy@linux.intel.com>,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] msi-x: let drivers retry when not enough vectors
Date: Thu, 07 May 2009 13:44:38 +0300 [thread overview]
Message-ID: <4A02BB96.8070103@redhat.com> (raw)
In-Reply-To: <1241691830.24385.6.camel@concordia>
Michael Ellerman wrote:
> Not to mention that there's no guarantee that you'll get as many
> interrupts as the device supports, so you should really be coding to
> cope with that anyway. Like the example in MSI-HOWTO.txt:
>
> 197 static int foo_driver_enable_msix(struct foo_adapter *adapter, int nvec)
> 198 {
> 199 while (nvec >= FOO_DRIVER_MINIMUM_NVEC) {
> 200 rc = pci_enable_msix(adapter->pdev,
> 201 adapter->msix_entries, nvec);
> 202 if (rc > 0)
> 203 nvec = rc;
> 204 else
> 205 return rc;
> 206 }
> 207
> 208 return -ENOSPC;
> 209 }
>
> So I agree, this patch is an improvement.
>
I imagine this loop is present in many drivers. So why not add a helper
static int pci_enable_msix_min(struct foo_adapter *adapter, int min_nvec)
{
int nvec = 2048;
while (nvec >= min_nvec) {
rc = pci_enable_msix(adapter->pdev,
adapter->msix_entries, nvec);
if (rc == 0)
return nvec;
else if (rc > 0)
nvec = rc;
else
return rc;
}
return -ENOSPC;
}
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-05-07 10:46 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 8:28 [PATCH] msi-x: let drivers retry when not enough vectors Michael S. Tsirkin
2009-05-07 8:51 ` Sheng Yang
2009-05-07 9:05 ` Michael S. Tsirkin
2009-05-07 9:10 ` Sheng Yang
2009-05-07 9:10 ` Sheng Yang
2009-05-07 9:31 ` Michael S. Tsirkin
2009-05-07 9:31 ` Michael S. Tsirkin
2009-05-07 9:05 ` Michael S. Tsirkin
2009-05-07 9:27 ` Matthew Wilcox
2009-05-07 9:40 ` Sheng Yang
2009-05-07 9:53 ` Matthew Wilcox
2009-05-07 10:19 ` Sheng Yang
2009-05-07 10:19 ` Sheng Yang
2009-05-07 10:32 ` Michael S. Tsirkin
2009-05-07 10:32 ` Michael S. Tsirkin
2009-05-07 23:55 ` Rusty Russell
2009-05-07 23:55 ` Rusty Russell
2009-05-08 0:22 ` Matthew Wilcox
2009-05-08 0:22 ` Matthew Wilcox
2009-05-08 0:28 ` Michael Ellerman
2009-05-08 0:28 ` Michael Ellerman
2009-05-12 21:28 ` Michael S. Tsirkin
2009-05-12 21:28 ` Michael S. Tsirkin
2009-05-07 10:23 ` Michael Ellerman
2009-05-07 10:23 ` Michael Ellerman
2009-05-07 10:28 ` Sheng Yang
2009-05-07 10:28 ` Sheng Yang
2009-05-07 10:44 ` Avi Kivity
2009-05-07 10:44 ` Avi Kivity [this message]
2009-05-07 11:57 ` Matthew Wilcox
2009-05-07 11:57 ` Matthew Wilcox
2009-05-07 9:53 ` Matthew Wilcox
2009-05-07 9:40 ` Sheng Yang
2009-05-07 9:27 ` Matthew Wilcox
2009-05-07 8:51 ` Sheng Yang
2009-06-11 18:28 ` Jesse Barnes
2009-06-11 18:28 ` Jesse Barnes
-- strict thread matches above, loose matches on Subject: below --
2009-05-07 8:28 Michael S. Tsirkin
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=4A02BB96.8070103@redhat.com \
--to=avi@redhat.com \
--cc=jbarnes@virtuousgeek.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=michael@ellerman.id.au \
--cc=mst@redhat.com \
--cc=sheng@linux.intel.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=willy@linux.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.