From: "Chen, Jing D" <jing.d.chen@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] doc: update nic overview
Date: Tue, 5 Apr 2016 08:49:24 +0000 [thread overview]
Message-ID: <4341B239C0EFF9468EE453F9E9F4604D0446DA34@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <7642275.Irj43jkQ8Y@xps13>
Thomas,
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Saturday, April 02, 2016 5:40 AM
> To: Chen, Jing D
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v2] doc: update nic overview
>
> 2016-04-01 16:55, Chen Jing D:
> > Add feature support list for fm10k, fm10k-vec, fm10kvf and
> > fm10kvf-vec.
>
> Please help me to understand what is fm10kvf.
> I see only one fm10k driver:
> % git grep 'struct eth_driver' drivers/net/fm10k/
> drivers/net/fm10k/fm10k_ethdev.c:static struct eth_driver rte_pmd_fm10k
> = {
You can refer to below definition:
static const struct rte_pci_id pci_id_fm10k_map[] = {
#define RTE_PCI_DEV_ID_DECL_FM10K(vend, dev) { RTE_PCI_DEVICE(vend, dev) },
#define RTE_PCI_DEV_ID_DECL_FM10KVF(vend, dev) { RTE_PCI_DEVICE(vend, dev) },
#include "rte_pci_dev_ids.h"
{ .vendor_id = 0, /* sentinel */ },
};
As you can see that fm10k driver will manage 2 different types of devices, PF and VF.
We can say that there are 2 drivers under fm10k directory. The aspects that not applicable
to PF/VF will use condition check to control execution path. This makes driver can work with
PF and VF devices and reduce redundant code.
next prev parent reply other threads:[~2016-04-05 8:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 8:39 [dpdk-dev] [PATCH] " Chen Jing D(Mark)
2016-04-01 8:55 ` [dpdk-dev] [PATCH v2] " Chen Jing D(Mark)
2016-04-01 21:40 ` Thomas Monjalon
2016-04-05 8:49 ` Chen, Jing D [this message]
2016-04-06 8:33 ` Thomas Monjalon
2016-04-07 7:54 ` Thomas Monjalon
2016-04-07 8:06 ` Chen, Jing D
2016-04-07 9:34 ` [dpdk-dev] [PATCH v3] " Chen Jing D(Mark)
2016-04-07 10:35 ` 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=4341B239C0EFF9468EE453F9E9F4604D0446DA34@shsmsx102.ccr.corp.intel.com \
--to=jing.d.chen@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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 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).