From: "Qiu, Michael" <michael.qiu@intel.com>
To: David Marchand <david.marchand@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] eal_pci: Fix max_vfs missing for none igb_uio driver
Date: Wed, 11 Feb 2015 12:41:15 +0000 [thread overview]
Message-ID: <533710CFB86FA344BFBF2D6802E60286CE8256@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <CALwxeUvkw-CrMKpw=v5=xxXWP2vpVKoiVRnN69JnSPrK5TaJyw@mail.gmail.com>
On 2/11/2015 8:32 PM, David Marchand wrote:
> Hello Michael,
>
> On Wed, Feb 11, 2015 at 12:10 PM, Michael Qiu <michael.qiu@intel.com
> <mailto:michael.qiu@intel.com>> wrote:
>
> max_vfs will only be created by igb_uio driver, for other
> drivers like vfio or pci_uio_generic, max_vfs will miss.
>
> But sriov_numvfs is not driver related, just get the vf numbers
> from that field.
>
> Signed-off-by: Michael Qiu <michael.qiu@intel.com
> <mailto:michael.qiu@intel.com>>
> ---
> lib/librte_eal/linuxapp/eal/eal_pci.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/librte_eal/linuxapp/eal/eal_pci.c
> b/lib/librte_eal/linuxapp/eal/eal_pci.c
> index 1f43688..3da4b69 100644
> --- a/lib/librte_eal/linuxapp/eal/eal_pci.c
> +++ b/lib/librte_eal/linuxapp/eal/eal_pci.c
> @@ -305,7 +305,7 @@ pci_scan_one(const char *dirname, uint16_t
> domain, uint8_t bus,
>
> /* get max_vfs */
> dev->max_vfs = 0;
> - snprintf(filename, sizeof(filename), "%s/max_vfs", dirname);
> + snprintf(filename, sizeof(filename), "%s/sriov_numvfs",
> dirname);
> if (!access(filename, F_OK) &&
> eal_parse_sysfs_value(filename, &tmp) == 0) {
> dev->max_vfs = (uint16_t)tmp;
>
>
> Not too sure about this change.
> Quickly looked, and as far as I can see, sriov_numvfs has been
> introduced by 1789382a ("PCI: SRIOV control and status via sysfs").
>
> Won't your change break anything that uses a kernel < 3.8 (not
> backported) ?
OK, you are right, I will fix this in v2, actually it will break nothing
as the code already done accessing check.
But not enough, for kernel version less than 3.8 and driver is igb_uio,
it is indeed not suitable for leaving max_vfs zero.
BTW, for kernel version less than 3.8 and driver is vfio or
pci_uio_generic, how could we fill this field?
Thanks,
Michael
>
>
> --
> David Marchand
next prev parent reply other threads:[~2015-02-11 12:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 11:10 Michael Qiu
2015-02-11 12:32 ` David Marchand
2015-02-11 12:41 ` Qiu, Michael [this message]
2015-02-11 13:25 ` [dpdk-dev] [PATCH v2] " Michael Qiu
2015-02-11 13:27 ` Qiu, Michael
2015-02-12 5:50 ` David Marchand
2015-02-13 3:01 ` Qiu, Michael
2015-02-13 13:49 ` Thomas Monjalon
2015-02-12 16:25 ` Thomas Monjalon
2015-02-13 2:56 ` Qiu, Michael
2015-02-13 9:20 ` Thomas Monjalon
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=533710CFB86FA344BFBF2D6802E60286CE8256@SHSMSX101.ccr.corp.intel.com \
--to=michael.qiu@intel.com \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.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).