From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id A8EF4DE0 for ; Thu, 9 Feb 2017 01:40:24 +0100 (CET) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga101.jf.intel.com with ESMTP; 08 Feb 2017 16:40:23 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.35,348,1484035200"; d="scan'208";a="1124016127" Received: from fmsmsx108.amr.corp.intel.com ([10.18.124.206]) by fmsmga002.fm.intel.com with ESMTP; 08 Feb 2017 16:40:23 -0800 Received: from fmsmsx125.amr.corp.intel.com (10.18.125.40) by FMSMSX108.amr.corp.intel.com (10.18.124.206) with Microsoft SMTP Server (TLS) id 14.3.248.2; Wed, 8 Feb 2017 16:40:23 -0800 Received: from shsmsx104.ccr.corp.intel.com (10.239.4.70) by FMSMSX125.amr.corp.intel.com (10.18.125.40) with Microsoft SMTP Server (TLS) id 14.3.248.2; Wed, 8 Feb 2017 16:40:22 -0800 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.88]) by SHSMSX104.ccr.corp.intel.com ([10.239.4.70]) with mapi id 14.03.0248.002; Thu, 9 Feb 2017 08:40:21 +0800 From: "Lu, Wenzhuo" To: "Yigit, Ferruh" , "dev@dpdk.org" Thread-Topic: [dpdk-dev] [PATCH] doc: announce ixgbe MTU setting limitation Thread-Index: AQHSgQqQ+cGBCJUvLUa8IEn4SvJCf6Few/gAgAET42A= Date: Thu, 9 Feb 2017 00:40:20 +0000 Message-ID: <6A0DE07E22DDAD4C9103DF62FEBC09093B5632B6@shsmsx102.ccr.corp.intel.com> References: <1486448555-95730-1-git-send-email-wenzhuo.lu@intel.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH] doc: announce ixgbe MTU setting limitation X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Feb 2017 00:40:25 -0000 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 limitatio= n >=20 > On 2/7/2017 6:22 AM, Wenzhuo Lu wrote: > > Signed-off-by: Wenzhuo Lu > > --- > > 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=3D0 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 > > ----------------------------------------- > > +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >=20 > This looks like the initial intention, thanks. >=20 > Also there are a few similar issues in the document: >=20 > 1) "Feature not Supported by RX Vector PMD" is under "TX Constraint". >=20 > 2) "Application Programming Interface" and "Sample Application Notes" > are under "Vector PMD for IXGBE" >=20 > Not sure if above are the intention. >=20 > What do you think converting this patch into a patchset, first patch fixe= s > headlines you already fixed and above ones if required. >=20 > And second patch is just to add "MTU setting" limitation note? Thanks for your suggestion. I'll split this patch. >=20 > Thanks, > ferruh >=20 > > > > 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 follo= ws: > > > > In order to ensure valid results, it is recommended to poll every 4 mi= nutes. > > > > +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 > > --------------------------- > >