DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: how to set VF MAC address on ixgbe
Date: Tue, 24 Oct 2017 00:31:12 +0000	[thread overview]
Message-ID: <6A0DE07E22DDAD4C9103DF62FEBC09093B6D8C9D@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE23EDE134A@IRSMSX103.ger.corp.intel.com>

Hi John,

> -----Original Message-----
> From: Mcnamara, John
> Sent: Monday, October 23, 2017 8:27 PM
> To: Lu, Wenzhuo <wenzhuo.lu@intel.com>; dev@dpdk.org
> Cc: Lu, Wenzhuo <wenzhuo.lu@intel.com>
> Subject: RE: [dpdk-dev] [PATCH] doc: how to set VF MAC address on ixgbe
> 
> 
> 
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Wenzhuo Lu
> > Sent: Monday, October 23, 2017 6:38 AM
> > To: dev@dpdk.org
> > Cc: Lu, Wenzhuo <wenzhuo.lu@intel.com>
> > Subject: [dpdk-dev] [PATCH] doc: how to set VF MAC address on ixgbe
> >
> > Add the description of how to add a MAC address for a VF from PF on
> ixgbe.
> >
> > Signed-off-by: Wenzhuo Lu <wenzhuo.lu@intel.com>
> > ---
> >  doc/guides/nics/ixgbe.rst | 11 +++++++++++
> >  1 file changed, 11 insertions(+)
> >
> > diff --git a/doc/guides/nics/ixgbe.rst b/doc/guides/nics/ixgbe.rst
> > index
> > 696ff69..bd0dc68 100644
> > --- a/doc/guides/nics/ixgbe.rst
> > +++ b/doc/guides/nics/ixgbe.rst
> > @@ -227,6 +227,17 @@ So when the user sets different MTUs on PF and
> VF
> > ports in one physical port,  the real MTU for all these PF and VF
> > ports is the largest value set.
> >  This behavior is based on the kernel driver behavior.
> >
> > +VF MAC address setting
> > +~~~~~~~~~~~~~~~~~~~~~~
> > +
> > +On ixgbe, the concept pool can be used for different things. It
> > +depends on the mode. In VMDq mode, the pool means a VMDq pool. In
> IOV
> > +mode, the pool means a VF.
> > +When setting the parameters of a pool, in VMDq mode, it's for a VMDq
> > +pool, in IOV mode, it's for a VF.
> > +There's no RTE API to add a VF's MAC address from PF. On ixgbe,
> > +there's a workaround to do it. "rte_eth_dev_mac_addr_add" also can be
> > +used to add a VF's MAC address.
> 
> I'd suggest something like the following may be a bit clearer:
> 
> VF MAC address setting
> ~~~~~~~~~~~~~~~~~~~~~~
> 
> On ixgbe, the concept of "pool" can be used for different things depending
> on the mode. In VMDq mode, "pool" means a VMDq pool. In IOV mode,
> "pool" means a VF.
> 
> There is no RTE API to add a VF's MAC address from the PF. On ixgbe, the
> ``rte_eth_dev_mac_addr_add()`` function can be can be used to add a VF's
> MAC address, as a workaround.
> 

Thanks for the suggestion. I'll send a V2.

  reply	other threads:[~2017-10-24  0:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-23  5:38 Wenzhuo Lu
2017-10-23 12:26 ` Mcnamara, John
2017-10-24  0:31   ` Lu, Wenzhuo [this message]
2017-10-24  0:57 ` [dpdk-dev] [PATCH v2] " Wenzhuo Lu
2017-11-01 21:51   ` Ferruh Yigit

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=6A0DE07E22DDAD4C9103DF62FEBC09093B6D8C9D@shsmsx102.ccr.corp.intel.com \
    --to=wenzhuo.lu@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@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 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).