From: Stefan Assmann <sassmann@kpanic.de>
To: Alexander Duyck <alexander.h.duyck@intel.com>
Cc: netdev@vger.kernel.org, e1000-devel@lists.sourceforge.net,
carolyn.wyborny@intel.com, gregory.v.rose@intel.com
Subject: Re: [PATCH net-next] igb: Change how we check for pre-existing and assigned VFs
Date: Thu, 16 Aug 2012 07:05:03 +0200 [thread overview]
Message-ID: <502C7F7F.1070101@kpanic.de> (raw)
In-Reply-To: <502BCA89.1030900@intel.com>
On 15.08.2012 18:12, Alexander Duyck wrote:
> On 08/14/2012 10:51 PM, Stefan Assmann wrote:
>> Adapt the pre-existing and assigned VFs code to the ixgbe way introduced
>> in commit 9297127b9cdd8d30c829ef5fd28b7cc0323a7bcd.
>>
>> Instead of searching the enabled VFs we use pci_num_vf to determine enabled VFs.
>> By comparing to which PF an assigned VF is owned it's possible to decide
>> whether to leave it enabled or not.
>>
>> Signed-off-by: Stefan Assmann <sassmann@kpanic.de>
[...]
>
> As the author of commit 9297127b9cdd8d30c829ef5fd28b7cc0323a7bcd it
> would have been nice to include me on the CC since I am probably one of
> the best people to review this patch. That being said, the patch itself
> looks good.
Sorry, my mistake. I forgot to do that.
>
> A follow-on patch that probably needs to be written would be to create a
> generic version of "vfs_are_assigned" as a part of the SR-IOV API. That
> way we can avoid duplicating the function in each of the drivers. All
> that would need to be changed is to pull the vendor ID from the pdev,
> and to pull the VF device ID from the SR-IOV configuration space of the
> physical function. I'll try to get to that sometime in the next few
> weeks if nobody gets to it before I do.
Sounds like a good idea.
>
> Acked-by: Alexander Duyck <alexander.h.duyck@intel.com>
>
Thanks for the review!
Stefan
prev parent reply other threads:[~2012-08-16 5:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-15 5:51 [PATCH net-next] igb: Change how we check for pre-existing and assigned VFs Stefan Assmann
2012-08-15 16:03 ` Greg Rose
2012-08-15 16:12 ` Alexander Duyck
2012-08-16 5:05 ` Stefan Assmann [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=502C7F7F.1070101@kpanic.de \
--to=sassmann@kpanic.de \
--cc=alexander.h.duyck@intel.com \
--cc=carolyn.wyborny@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=gregory.v.rose@intel.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 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.