All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sheng Yang <sheng@linux.intel.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: kvm@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	jbarnes@virtuousgeek.org,
	virtualization@lists.linux-foundation.org,
	Matthew Wilcox <willy@linux.intel.com>
Subject: Re: [PATCH] msi-x: let drivers retry when not enough vectors
Date: Thu, 7 May 2009 17:40:15 +0800	[thread overview]
Message-ID: <200905071740.16190.sheng__9082.71242301471$1241689292$gmane$org@linux.intel.com> (raw)
In-Reply-To: <20090507092731.GH8112@parisc-linux.org>

On Thursday 07 May 2009 17:27:31 Matthew Wilcox wrote:
> On Thu, May 07, 2009 at 04:51:24PM +0800, Sheng Yang wrote:
> > On Thursday 07 May 2009 16:28:41 Michael S. Tsirkin wrote:
> > > pci_enable_msix currently returns -EINVAL if you ask
> > > for more vectors than supported by the device, which would
> > > typically cause fallback to regular interrupts.
> > >
> > > It's better to return the table size, making the driver retry
> > > MSI-X with less vectors.
> >
> > Hi Michael
> >
> > I think driver should read from capability list to know how many vector
> > supported by this device before enable MSI-X for device, as
> > pci_msix_table_size() did...
>
> I think Michael's patch makes sense.  It reduces the amount of work the
> driver has to do without requiring any additional work in the core.  I
> don't see the disadvantage to it.
>
> Reviewed-by: Matthew Wilcox <willy@linux.intel.com>

It's indeed weird. Why the semantic of pci_enable_msix can be changed to 
"enable msix, or tell me how many vector do you have"? You can simply call 
pci_msix_table_size() to get what you want, also without any more work, no? I 
can't understand...

-- 
regards
Yang, Sheng

  reply	other threads:[~2009-05-07  9:40 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:27   ` Matthew Wilcox
2009-05-07  9:40     ` Sheng Yang [this message]
2009-05-07  9:40     ` Sheng Yang
2009-05-07  9:53       ` Matthew Wilcox
2009-05-07  9:53       ` Matthew Wilcox
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:19         ` Sheng Yang
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
2009-05-07 11:57             ` Matthew Wilcox
2009-05-07 11:57             ` Matthew Wilcox
2009-05-07  8:51 ` Sheng Yang
2009-06-11 18:28 ` Jesse Barnes
2009-06-11 18:28 ` Jesse Barnes
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='200905071740.16190.sheng__9082.71242301471$1241689292$gmane$org@linux.intel.com' \
    --to=sheng@linux.intel.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=mst@redhat.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.