From: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: announce ixgbe MTU setting limitation
Date: Thu, 9 Feb 2017 00:40:20 +0000 [thread overview]
Message-ID: <6A0DE07E22DDAD4C9103DF62FEBC09093B5632B6@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <bfc061b7-a90d-d51a-d5a3-22b69da2dabc@intel.com>
Hi Ferruh,
> -----Original Message-----
> From: Yigit, Ferruh
> Sent: Thursday, February 9, 2017 12:12 AM
> To: Lu, Wenzhuo; dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] doc: announce ixgbe MTU setting limitation
>
> On 2/7/2017 6:22 AM, Wenzhuo Lu wrote:
> > Signed-off-by: Wenzhuo Lu <wenzhuo.lu@intel.com>
> > ---
> > doc/guides/nics/ixgbe.rst | 16 ++++++++++++++--
> > 1 file changed, 14 insertions(+), 2 deletions(-)
> >
> > diff --git a/doc/guides/nics/ixgbe.rst b/doc/guides/nics/ixgbe.rst
> > index 3b6851b..1f7d6b3 100644
> > --- a/doc/guides/nics/ixgbe.rst
> > +++ b/doc/guides/nics/ixgbe.rst
> > @@ -185,8 +185,11 @@ As in the case of l3fwd, set configure
> > port_conf.rxmode.hw_ip_checksum=0 to enab In addition, for improved
> performance, use -bsz "(32,32),(64,64),(32,32)" in load_balancer to avoid using
> the default burst size of 144.
> >
> >
> > +Limitations or Known issues
> > +---------------------------
> > +
> > Malicious Driver Detection not Supported
> > -----------------------------------------
> > +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> This looks like the initial intention, thanks.
>
> Also there are a few similar issues in the document:
>
> 1) "Feature not Supported by RX Vector PMD" is under "TX Constraint".
>
> 2) "Application Programming Interface" and "Sample Application Notes"
> are under "Vector PMD for IXGBE"
>
> Not sure if above are the intention.
>
> What do you think converting this patch into a patchset, first patch fixes
> headlines you already fixed and above ones if required.
>
> And second patch is just to add "MTU setting" limitation note?
Thanks for your suggestion. I'll split this patch.
>
> Thanks,
> ferruh
>
> >
> > The Intel x550 series NICs support a feature called MDD (Malicious
> > Driver Detection) which checks the behavior of the VF driver.
> > @@ -207,7 +210,7 @@ it by default.)
> >
> >
> > Statistics
> > -----------
> > +~~~~~~~~~~
> >
> > The statistics of ixgbe hardware must be polled regularly in order
> > for it to remain consistent. Running a DPDK application without
> > polling the statistics will @@ -230,6 +233,15 @@ be calculated as follows:
> >
> > In order to ensure valid results, it is recommended to poll every 4 minutes.
> >
> > +MTU setting
> > +~~~~~~~~~~~
> > +
> > +Although user can set MTU separately on PF and VF ports, ixgbe only
> > +supports one global MTU per physical port.
> > +So when 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 biggest one.
> > +This behavior is leveraged from kernel driver.
> > +
> >
> > Supported Chipsets and NICs
> > ---------------------------
> >
next prev parent reply other threads:[~2017-02-09 0:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 6:22 Wenzhuo Lu
2017-02-08 16:12 ` Ferruh Yigit
2017-02-09 0:40 ` Lu, Wenzhuo [this message]
2017-02-08 17:10 ` Mcnamara, John
2017-02-09 0:42 ` Lu, Wenzhuo
2017-02-09 1:27 ` [dpdk-dev] [PATCH v2 0/2] update ixgbe doc Wenzhuo Lu
2017-02-09 1:27 ` [dpdk-dev] [PATCH v2 1/2] doc: fix framework of " Wenzhuo Lu
2017-02-09 15:05 ` [dpdk-dev] [dpdk-stable] " Mcnamara, John
2017-02-09 1:28 ` [dpdk-dev] [PATCH v2 2/2] doc: announce ixgbe MTU setting limitation Wenzhuo Lu
2017-02-09 15:05 ` Mcnamara, John
2017-02-09 15:28 ` [dpdk-dev] [PATCH v2 0/2] update ixgbe doc 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=6A0DE07E22DDAD4C9103DF62FEBC09093B5632B6@shsmsx102.ccr.corp.intel.com \
--to=wenzhuo.lu@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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).