From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id BE24D47D1 for ; Tue, 6 Dec 2016 13:49:16 +0100 (CET) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga103.jf.intel.com with ESMTP; 06 Dec 2016 04:47:11 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,310,1477983600"; d="scan'208";a="794827885" Received: from irsmsx102.ger.corp.intel.com ([163.33.3.155]) by FMSMGA003.fm.intel.com with ESMTP; 06 Dec 2016 04:47:10 -0800 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.91]) by IRSMSX102.ger.corp.intel.com ([169.254.2.79]) with mapi id 14.03.0248.002; Tue, 6 Dec 2016 12:46:58 +0000 From: "Mcnamara, John" To: "Yigit, Ferruh" , Alejandro Lucero , "dev@dpdk.org" Thread-Topic: [dpdk-dev] [PATCH] nfp: add doc about supported features Thread-Index: AQHSTHSZc1o+RdDdKUiLZG0bBpvRLKD62fwAgAAIqTA= Date: Tue, 6 Dec 2016 12:46:57 +0000 Message-ID: References: <1480666653-35544-1-git-send-email-alejandro.lucero@netronome.com> <3133b0c5-672d-de7d-1690-815c7603e581@intel.com> In-Reply-To: <3133b0c5-672d-de7d-1690-815c7603e581@intel.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_IC x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMDg2YjdiZTAtMTE2Ny00MDc5LTk4OTgtODAwZmFiZDQ0MmEzIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6Ikg5dnY2Y0RcL3MwUlR2djViRlVqaDE5SnBKbTVIYXJhNkhTV1NHUnlJdjVFPSJ9 x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH] nfp: add doc about supported features 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: Tue, 06 Dec 2016 12:49:17 -0000 > -----Original Message----- > From: Yigit, Ferruh > Sent: Tuesday, December 6, 2016 12:08 PM > To: Alejandro Lucero ; dev@dpdk.org; > Mcnamara, John > Subject: Re: [dpdk-dev] [PATCH] nfp: add doc about supported features >=20 > On 12/2/2016 8:17 AM, Alejandro Lucero wrote: > > Signed-off-by: Alejandro Lucero > > --- > > doc/guides/nics/features/nfp.ini | 25 +++++++++++++++++++++++++ > > 1 file changed, 25 insertions(+) > > > > diff --git a/doc/guides/nics/features/nfp.ini > b/doc/guides/nics/features/nfp.ini > > index d967151..dd78233 100644 > > --- a/doc/guides/nics/features/nfp.ini > > +++ b/doc/guides/nics/features/nfp.ini > > @@ -4,3 +4,28 @@ > > ; Refer to default.ini for the full list of available PMD features. > > ; > > [Features] > > +SR-IOV =3D Y > > +Link status =3D Y > > +Link status event =3D Y > > +Rx interrupt =3D N >=20 > Hi John, >=20 > Do we support 'N'? Since this is the first 'N' in the table. >=20 > I guess not having a value implies feature is not supported. N or any other single letter is supported. The nice thing about it is that it is explicitly NO rather than implicitly = NO. However, if all the nics filled in the NOes then the table might be har= d to read. So, for consistency it is probably best to just let the unsupported feature= s be blank.