21/03/2018 15:31, Qiming Yang:
> - <li><a href="/doc/guides/nics/i40e.html">i40e</a> (X710, XL710, X722)</li>
> + <li><a href="/doc/guides/nics/i40e.html">i40e</a> (X710, XL710, X722, XXV710)</li>
Please, could add in the message which release is supporting this device?
> -----Original Message-----
> From: web [mailto:web-bounces@dpdk.org] On Behalf Of Qiming Yang
> Sent: Wednesday, March 21, 2018 2:31 PM
> To: Yang, Qiming <qiming.yang@intel.com>; web@dpdk.org
> Subject: [dpdk-web] [PATCH] add XXV710 to i40e suppported NICs
>
> Signed-off-by: Qiming Yang <qiming.yang@intel.com>
Acked-by: John McNamara <john.mcnamara@intel.com>
> -----Original Message-----
> From: web [mailto:web-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Wednesday, March 21, 2018 8:30 AM
> To: Yang, Qiming <qiming.yang@intel.com>
> Cc: web@dpdk.org
> Subject: Re: [dpdk-web] [PATCH] add XXV710 to i40e suppported NICs
>
> 21/03/2018 15:31, Qiming Yang:
> > - <li><a href="/doc/guides/nics/i40e.html">i40e</a>
> (X710, XL710, X722)</li>
> > + <li><a href="/doc/guides/nics/i40e.html">i40e</a>
> (X710, XL710, X722, XXV710)</li>
>
> Please, could add in the message which release is supporting this device?
Just to clarify, you mean to add the release in the commit message not the html, right?
John
21/03/2018 10:18, Mcnamara, John:
>
> > -----Original Message-----
> > From: web [mailto:web-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> > Sent: Wednesday, March 21, 2018 8:30 AM
> > To: Yang, Qiming <qiming.yang@intel.com>
> > Cc: web@dpdk.org
> > Subject: Re: [dpdk-web] [PATCH] add XXV710 to i40e suppported NICs
> >
> > 21/03/2018 15:31, Qiming Yang:
> > > - <li><a href="/doc/guides/nics/i40e.html">i40e</a>
> > (X710, XL710, X722)</li>
> > > + <li><a href="/doc/guides/nics/i40e.html">i40e</a>
> > (X710, XL710, X722, XXV710)</li>
> >
> > Please, could add in the message which release is supporting this device?
>
>
> Just to clarify, you mean to add the release in the commit message not the html, right?
Yes, just for the history, and for justification.
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> Sent: Wednesday, March 21, 2018 9:21 AM
> To: Mcnamara, John <john.mcnamara@intel.com>
> Cc: Yang, Qiming <qiming.yang@intel.com>; web@dpdk.org
> Subject: Re: [dpdk-web] [PATCH] add XXV710 to i40e suppported NICs
>
> 21/03/2018 10:18, Mcnamara, John:
> >
> > > -----Original Message-----
> > > From: web [mailto:web-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> > > Sent: Wednesday, March 21, 2018 8:30 AM
> > > To: Yang, Qiming <qiming.yang@intel.com>
> > > Cc: web@dpdk.org
> > > Subject: Re: [dpdk-web] [PATCH] add XXV710 to i40e suppported NICs
> > >
> > > 21/03/2018 15:31, Qiming Yang:
> > > > - <li><a
> href="/doc/guides/nics/i40e.html">i40e</a>
> > > (X710, XL710, X722)</li>
> > > > + <li><a
> href="/doc/guides/nics/i40e.html">i40e</a>
> > > (X710, XL710, X722, XXV710)</li>
> > >
> > > Please, could add in the message which release is supporting this
> device?
> >
> >
> > Just to clarify, you mean to add the release in the commit message not
> the html, right?
>
> Yes, just for the history, and for justification.
Ok. Qiming, could you submit a V2 with a commit message that states when
XXV710 support was added.
Signed-off-by: Qiming Yang <qiming.yang@intel.com> --- doc/nics.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/nics.html b/doc/nics.html index ffe4455..58d6bf8 100644 --- a/doc/nics.html +++ b/doc/nics.html @@ -75,7 +75,7 @@ <li><a href="/browse/dpdk/tree/drivers/net/e1000/">e1000e</a> (82571, 82572, 82573, 82574, 82583, ICH8, ICH9, ICH10, PCH, PCH2, I217, I218, I219)</li> <li><a href="/browse/dpdk/tree/drivers/net/e1000/">igb</a> (82575, 82576, 82580, I210, I211, I350, I354, DH89xx)</li> <li><a href="/doc/guides/nics/ixgbe.html">ixgbe</a> (82598, 82599, X520, X540, X550)</li> - <li><a href="/doc/guides/nics/i40e.html">i40e</a> (X710, XL710, X722)</li> + <li><a href="/doc/guides/nics/i40e.html">i40e</a> (X710, XL710, X722, XXV710)</li> <li><a href="/doc/guides/nics/fm10k.html">fm10k</a> (FM10420)</li> </ul> <p>Note: The drivers <em>e1000</em> and <em>e1000e</em> are also called <em>em</em>. -- 2.9.5
Signed-off-by: Qiming Yang <qiming.yang@intel.com> --- doc/nics.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/nics.html b/doc/nics.html index ffe4455..58d6bf8 100644 --- a/doc/nics.html +++ b/doc/nics.html @@ -75,7 +75,7 @@ <li><a href="/browse/dpdk/tree/drivers/net/e1000/">e1000e</a> (82571, 82572, 82573, 82574, 82583, ICH8, ICH9, ICH10, PCH, PCH2, I217, I218, I219)</li> <li><a href="/browse/dpdk/tree/drivers/net/e1000/">igb</a> (82575, 82576, 82580, I210, I211, I350, I354, DH89xx)</li> <li><a href="/doc/guides/nics/ixgbe.html">ixgbe</a> (82598, 82599, X520, X540, X550)</li> - <li><a href="/doc/guides/nics/i40e.html">i40e</a> (X710, XL710, X722)</li> + <li><a href="/doc/guides/nics/i40e.html">i40e</a> (X710, XL710, X722, XXV710)</li> <li><a href="/doc/guides/nics/fm10k.html">fm10k</a> (FM10420)</li> </ul> <p>Note: The drivers <em>e1000</em> and <em>e1000e</em> are also called <em>em</em>. -- 2.9.5
Signed-off-by: Qiming Yang <qiming.yang@intel.com> --- doc/nics.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/nics.html b/doc/nics.html index ffe4455..58d6bf8 100644 --- a/doc/nics.html +++ b/doc/nics.html @@ -75,7 +75,7 @@ <li><a href="/browse/dpdk/tree/drivers/net/e1000/">e1000e</a> (82571, 82572, 82573, 82574, 82583, ICH8, ICH9, ICH10, PCH, PCH2, I217, I218, I219)</li> <li><a href="/browse/dpdk/tree/drivers/net/e1000/">igb</a> (82575, 82576, 82580, I210, I211, I350, I354, DH89xx)</li> <li><a href="/doc/guides/nics/ixgbe.html">ixgbe</a> (82598, 82599, X520, X540, X550)</li> - <li><a href="/doc/guides/nics/i40e.html">i40e</a> (X710, XL710, X722)</li> + <li><a href="/doc/guides/nics/i40e.html">i40e</a> (X710, XL710, X722, XXV710)</li> <li><a href="/doc/guides/nics/fm10k.html">fm10k</a> (FM10420)</li> </ul> <p>Note: The drivers <em>e1000</em> and <em>e1000e</em> are also called <em>em</em>. -- 2.9.5
From: Qiming Yang <qiming.yang@intel.com> Signed-off-by: Qiming Yang <qiming.yang@intel.com> --- doc/nics.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/nics.html b/doc/nics.html index ffe4455..58d6bf8 100644 --- a/doc/nics.html +++ b/doc/nics.html @@ -75,7 +75,7 @@ <li><a href="/browse/dpdk/tree/drivers/net/e1000/">e1000e</a> (82571, 82572, 82573, 82574, 82583, ICH8, ICH9, ICH10, PCH, PCH2, I217, I218, I219)</li> <li><a href="/browse/dpdk/tree/drivers/net/e1000/">igb</a> (82575, 82576, 82580, I210, I211, I350, I354, DH89xx)</li> <li><a href="/doc/guides/nics/ixgbe.html">ixgbe</a> (82598, 82599, X520, X540, X550)</li> - <li><a href="/doc/guides/nics/i40e.html">i40e</a> (X710, XL710, X722)</li> + <li><a href="/doc/guides/nics/i40e.html">i40e</a> (X710, XL710, X722, XXV710)</li> <li><a href="/doc/guides/nics/fm10k.html">fm10k</a> (FM10420)</li> </ul> <p>Note: The drivers <em>e1000</em> and <em>e1000e</em> are also called <em>em</em>. -- 2.9.5
> -----Original Message----- > From: Lu, Wenzhuo > Sent: Wednesday, May 16, 2018 10:32 AM > To: web@dpdk.org > Cc: Yang, Qiming > Subject: [PATCH] add XXV710 to i40e suppported NICs > > From: Qiming Yang <qiming.yang@intel.com> > > Signed-off-by: Qiming Yang <qiming.yang@intel.com> Acked-by: Helin Zhang <helin.zhang@intel.com> > --- > doc/nics.html | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/doc/nics.html b/doc/nics.html index ffe4455..58d6bf8 100644 > --- a/doc/nics.html > +++ b/doc/nics.html > @@ -75,7 +75,7 @@ > <li><a > href="/browse/dpdk/tree/drivers/net/e1000/">e1000e</a> (82571, 82572, > 82573, 82574, 82583, ICH8, ICH9, ICH10, PCH, PCH2, I217, I218, I219)</li> > <li><a > href="/browse/dpdk/tree/drivers/net/e1000/">igb</a> (82575, 82576, 82580, > I210, I211, I350, I354, DH89xx)</li> > <li><a > href="/doc/guides/nics/ixgbe.html">ixgbe</a> (82598, 82599, X520, X540, > X550)</li> > - <li><a > href="/doc/guides/nics/i40e.html">i40e</a> (X710, XL710, X722)</li> > + <li><a > href="/doc/guides/nics/i40e.html">i40e</a> (X710, XL710, > +X722, XXV710)</li> > <li><a > href="/doc/guides/nics/fm10k.html">fm10k</a> (FM10420)</li> > </ul> > <p>Note: The drivers <em>e1000</em> and > <em>e1000e</em> are also called <em>em</em>. > -- > 2.9.5
> -----Original Message-----
> From: web [mailto:web-bounces@dpdk.org] On Behalf Of Wenzhuo Lu
> Sent: Wednesday, May 16, 2018 3:32 AM
> To: web@dpdk.org
> Cc: Yang, Qiming <qiming.yang@intel.com>
> Subject: [dpdk-web] [PATCH] add XXV710 to i40e suppported NICs
>
> From: Qiming Yang <qiming.yang@intel.com>
>
> Signed-off-by: Qiming Yang <qiming.yang@intel.com>
Acked-by: John McNamara <john.mcnamara@intel.com>
Signed-off-by: Qiming Yang <qiming.yang@intel.com> --- doc/nics.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/nics.html b/doc/nics.html index ffe4455..58d6bf8 100644 --- a/doc/nics.html +++ b/doc/nics.html @@ -75,7 +75,7 @@ <li><a href="/browse/dpdk/tree/drivers/net/e1000/">e1000e</a> (82571, 82572, 82573, 82574, 82583, ICH8, ICH9, ICH10, PCH, PCH2, I217, I218, I219)</li> <li><a href="/browse/dpdk/tree/drivers/net/e1000/">igb</a> (82575, 82576, 82580, I210, I211, I350, I354, DH89xx)</li> <li><a href="/doc/guides/nics/ixgbe.html">ixgbe</a> (82598, 82599, X520, X540, X550)</li> - <li><a href="/doc/guides/nics/i40e.html">i40e</a> (X710, XL710, X722)</li> + <li><a href="/doc/guides/nics/i40e.html">i40e</a> (X710, XL710, X722, XXV710)</li> <li><a href="/doc/guides/nics/fm10k.html">fm10k</a> (FM10420)</li> </ul> <p>Note: The drivers <em>e1000</em> and <em>e1000e</em> are also called <em>em</em>. -- 2.9.5
16/05/2018 11:51, Qiming Yang:
> Signed-off-by: Qiming Yang <qiming.yang@intel.com>
Please add some details in the commit message:
support has been added in which release?
Is there a commit id to reference?
16/05/2018 04:32, Wenzhuo Lu:
> From: Qiming Yang <qiming.yang@intel.com>
>
> Signed-off-by: Qiming Yang <qiming.yang@intel.com>
Qiming sent a duplicate after this one.
BTW, same comments as other patch:
Please add some details in the commit message:
support has been added in which release?
Is there a commit id to reference?
17/05/2018 15:15, Thomas Monjalon:
> 16/05/2018 11:51, Qiming Yang:
> > Signed-off-by: Qiming Yang <qiming.yang@intel.com>
>
> Please add some details in the commit message:
> support has been added in which release?
> Is there a commit id to reference?
Any feedback please?
Would be nice to have it for the release tomorrow.
From: Qiming Yang <qiming.yang@intel.com> XXV710 is pre-enabled on v16.11 and be validated on v17.02. Reference commit: 75d133dd32963c6897f97077c270082f1b4fef4e Signed-off-by: Qiming Yang <qiming.yang@intel.com> --- doc/nics.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/nics.html b/doc/nics.html index ffe4455..58d6bf8 100644 --- a/doc/nics.html +++ b/doc/nics.html @@ -75,7 +75,7 @@ <li><a href="/browse/dpdk/tree/drivers/net/e1000/">e1000e</a> (82571, 82572, 82573, 82574, 82583, ICH8, ICH9, ICH10, PCH, PCH2, I217, I218, I219)</li> <li><a href="/browse/dpdk/tree/drivers/net/e1000/">igb</a> (82575, 82576, 82580, I210, I211, I350, I354, DH89xx)</li> <li><a href="/doc/guides/nics/ixgbe.html">ixgbe</a> (82598, 82599, X520, X540, X550)</li> - <li><a href="/doc/guides/nics/i40e.html">i40e</a> (X710, XL710, X722)</li> + <li><a href="/doc/guides/nics/i40e.html">i40e</a> (X710, XL710, X722, XXV710)</li> <li><a href="/doc/guides/nics/fm10k.html">fm10k</a> (FM10420)</li> </ul> <p>Note: The drivers <em>e1000</em> and <em>e1000e</em> are also called <em>em</em>. -- 2.9.5
29/05/2018 04:19, Wenzhuo Lu:
> From: Qiming Yang <qiming.yang@intel.com>
>
> XXV710 is pre-enabled on v16.11 and be validated on v17.02.
>
> Reference commit: 75d133dd32963c6897f97077c270082f1b4fef4e
>
> Signed-off-by: Qiming Yang <qiming.yang@intel.com>
Applied, thanks
On 5/29/2018 9:00 AM, Thomas Monjalon wrote: > 29/05/2018 04:19, Wenzhuo Lu: >> From: Qiming Yang <qiming.yang@intel.com> >> >> XXV710 is pre-enabled on v16.11 and be validated on v17.02. >> >> Reference commit: 75d133dd32963c6897f97077c270082f1b4fef4e >> >> Signed-off-by: Qiming Yang <qiming.yang@intel.com> > > Applied, thanks Hi Thomas, I can't see this information (XXV710 as supported NIC) in the web page, it may be lost somehow, how can we add it back? And supported hardware information is presented in two different location in webpage: https://core.dpdk.org/supported/ https://www.dpdk.org/ecosystem/#hardware Can we reduce it into single place? Is ecosystem good place for listing hardware support? And as last, formatting of multiple device listing is not good, it is almost not readable for Intel ones on https://core.dpdk.org/supported/, how can we fix it? Thanks, ferruh
28/06/2018 18:45, Ferruh Yigit: > On 5/29/2018 9:00 AM, Thomas Monjalon wrote: > > 29/05/2018 04:19, Wenzhuo Lu: > >> From: Qiming Yang <qiming.yang@intel.com> > >> > >> XXV710 is pre-enabled on v16.11 and be validated on v17.02. > >> > >> Reference commit: 75d133dd32963c6897f97077c270082f1b4fef4e > >> > >> Signed-off-by: Qiming Yang <qiming.yang@intel.com> > > > > Applied, thanks > > Hi Thomas, > > I can't see this information (XXV710 as supported NIC) in the web page, it may > be lost somehow, how can we add it back? Yes it has been lost with other NICs recent update when migrating. I have fixed it for core.dpdk.org (see the patch below). Thanks for the report. > And supported hardware information is presented in two different location in > webpage: > https://core.dpdk.org/supported/ > https://www.dpdk.org/ecosystem/#hardware > > Can we reduce it into single place? > Is ecosystem good place for listing hardware support? I think the intent of the ecosystem page was to show a diversity of vendors. I think we don't need all the details here. As it is more a technical DPDK info, I think it should be in core.dpdk.org. And it will be easier to update the device models regularly and precisely with patches. I suggest to limit the ecosystem page at vendor names, add CPU and other HW, and point to the core.dpdk.org page for details. > And as last, formatting of multiple device listing is not good, it is almost not > readable for Intel ones on https://core.dpdk.org/supported/, how can we fix it? Yes, this the format proposed in the first version drafted by the Linux Foundation. I have not changed it because I am not sure what is better. There is a nice page well formatted for each vendor when clicking on the name. Example: https://core.dpdk.org/supported/nics/intel/ --------------------- --- a/content/supported/NICs/intel.md +++ b/content/supported/NICs/intel.md @@ -10,7 +10,7 @@ weight = "7" - [e1000e](http://git.dpdk.org/dpdk/tree/drivers/net/e1000/) (82571, 82572, 82573, 82574, 82583, ICH8, ICH9, ICH10, PCH, PCH2, I217, I218, I219) - [igb](http://doc.dpdk.org/guides/nics/igb.html) (82575, 82576, 82580, I210, I211, I350, I354, DH89xx) - [ixgbe](http://doc.dpdk.org/guides/nics/ixgbe.html) (82598, 82599, X520, X540, X550) -- [i40e](http://doc.dpdk.org/guides/nics/i40e.html) (X710, XL710, X722) +- [i40e](http://doc.dpdk.org/guides/nics/i40e.html) (X710, XL710, X722, XXV710) - [fm10k](http://doc.dpdk.org/guides/nics/fm10k.html) (FM10420) {{% notice note %}} --- a/content/supported/NICs/marvell.md +++ b/content/supported/NICs/marvell.md @@ -6,4 +6,4 @@ type = "nic" weight = "8" +++ -- [mrvl](http://doc.dpdk.org/guides/nics/mvpp2.html) (Marvell Packet Processor v2) +- [mvpp2](http://doc.dpdk.org/guides/nics/mvpp2.html) (Marvell Packet Processor v2) --- a/content/supported/NICs/mellanox.md +++ b/content/supported/NICs/mellanox.md @@ -7,4 +7,4 @@ weight = "9" +++ - [mlx4](http://doc.dpdk.org/guides/nics/mlx4.html) (ConnectX-3, ConnectX-3 Pro) -- [mlx5](http://doc.dpdk.org/guides/nics/mlx5.html) (ConnectX-4, ConnectX-4 Lx, ConnectX-5) +- [mlx5](http://doc.dpdk.org/guides/nics/mlx5.html) (ConnectX-4, ConnectX-4 Lx, ConnectX-5, Bluefield) --- a/content/supported/NICs/solarflare.md +++ b/content/supported/NICs/solarflare.md @@ -6,4 +6,4 @@ type = "nic" weight = "13" +++ -- [sfc_efx](http://doc.dpdk.org/guides/nics/sfc_efx.html) (SFN7xxx, SFN8xxx) +- [sfc_efx](http://doc.dpdk.org/guides/nics/sfc_efx.html) (SFN7xxx, SFN8xxx, XtremeScale X2)
On 6/28/2018 9:11 PM, Thomas Monjalon wrote: > 28/06/2018 18:45, Ferruh Yigit: >> On 5/29/2018 9:00 AM, Thomas Monjalon wrote: >>> 29/05/2018 04:19, Wenzhuo Lu: >>>> From: Qiming Yang <qiming.yang@intel.com> >>>> >>>> XXV710 is pre-enabled on v16.11 and be validated on v17.02. >>>> >>>> Reference commit: 75d133dd32963c6897f97077c270082f1b4fef4e >>>> >>>> Signed-off-by: Qiming Yang <qiming.yang@intel.com> >>> >>> Applied, thanks >> >> Hi Thomas, >> >> I can't see this information (XXV710 as supported NIC) in the web page, it may >> be lost somehow, how can we add it back? > > Yes it has been lost with other NICs recent update when migrating. > I have fixed it for core.dpdk.org (see the patch below). Looks good, thanks. > Thanks for the report. > > >> And supported hardware information is presented in two different location in >> webpage: >> https://core.dpdk.org/supported/ >> https://www.dpdk.org/ecosystem/#hardware >> >> Can we reduce it into single place? >> Is ecosystem good place for listing hardware support? > > I think the intent of the ecosystem page was to show a diversity of vendors. > I think we don't need all the details here. > As it is more a technical DPDK info, I think it should be in core.dpdk.org. > And it will be easier to update the device models regularly and precisely with patches. > > I suggest to limit the ecosystem page at vendor names, add CPU and other HW, > and point to the core.dpdk.org page for details. +1 > > >> And as last, formatting of multiple device listing is not good, it is almost not >> readable for Intel ones on https://core.dpdk.org/supported/, how can we fix it? > > Yes, this the format proposed in the first version drafted by the Linux Foundation. > I have not changed it because I am not sure what is better. > There is a nice page well formatted for each vendor when clicking on the name. > Example: > https://core.dpdk.org/supported/nics/intel/ Yes this page look better, I think it is better to have similar view in support page. > > > --------------------- > > --- a/content/supported/NICs/intel.md > +++ b/content/supported/NICs/intel.md > @@ -10,7 +10,7 @@ weight = "7" > - [e1000e](http://git.dpdk.org/dpdk/tree/drivers/net/e1000/) (82571, 82572, 82573, 82574, 82583, ICH8, ICH9, ICH10, PCH, PCH2, I217, I218, I219) > - [igb](http://doc.dpdk.org/guides/nics/igb.html) (82575, 82576, 82580, I210, I211, I350, I354, DH89xx) > - [ixgbe](http://doc.dpdk.org/guides/nics/ixgbe.html) (82598, 82599, X520, X540, X550) > -- [i40e](http://doc.dpdk.org/guides/nics/i40e.html) (X710, XL710, X722) > +- [i40e](http://doc.dpdk.org/guides/nics/i40e.html) (X710, XL710, X722, XXV710) > - [fm10k](http://doc.dpdk.org/guides/nics/fm10k.html) (FM10420) > > {{% notice note %}} > > --- a/content/supported/NICs/marvell.md > +++ b/content/supported/NICs/marvell.md > @@ -6,4 +6,4 @@ type = "nic" > weight = "8" > +++ > > -- [mrvl](http://doc.dpdk.org/guides/nics/mvpp2.html) (Marvell Packet Processor v2) > +- [mvpp2](http://doc.dpdk.org/guides/nics/mvpp2.html) (Marvell Packet Processor v2) > > --- a/content/supported/NICs/mellanox.md > +++ b/content/supported/NICs/mellanox.md > @@ -7,4 +7,4 @@ weight = "9" > +++ > > - [mlx4](http://doc.dpdk.org/guides/nics/mlx4.html) (ConnectX-3, ConnectX-3 Pro) > -- [mlx5](http://doc.dpdk.org/guides/nics/mlx5.html) (ConnectX-4, ConnectX-4 Lx, ConnectX-5) > +- [mlx5](http://doc.dpdk.org/guides/nics/mlx5.html) (ConnectX-4, ConnectX-4 Lx, ConnectX-5, Bluefield) > > --- a/content/supported/NICs/solarflare.md > +++ b/content/supported/NICs/solarflare.md > @@ -6,4 +6,4 @@ type = "nic" > weight = "13" > +++ > > -- [sfc_efx](http://doc.dpdk.org/guides/nics/sfc_efx.html) (SFN7xxx, SFN8xxx) > +- [sfc_efx](http://doc.dpdk.org/guides/nics/sfc_efx.html) (SFN7xxx, SFN8xxx, XtremeScale X2) > > >
On 7/2/2018 11:32 AM, Ferruh Yigit wrote: > On 6/28/2018 9:11 PM, Thomas Monjalon wrote: >> 28/06/2018 18:45, Ferruh Yigit: >>> On 5/29/2018 9:00 AM, Thomas Monjalon wrote: >>>> 29/05/2018 04:19, Wenzhuo Lu: >>>>> From: Qiming Yang <qiming.yang@intel.com> >>>>> >>>>> XXV710 is pre-enabled on v16.11 and be validated on v17.02. >>>>> >>>>> Reference commit: 75d133dd32963c6897f97077c270082f1b4fef4e >>>>> >>>>> Signed-off-by: Qiming Yang <qiming.yang@intel.com> >>>> >>>> Applied, thanks >>> >>> Hi Thomas, >>> >>> I can't see this information (XXV710 as supported NIC) in the web page, it may >>> be lost somehow, how can we add it back? >> >> Yes it has been lost with other NICs recent update when migrating. >> I have fixed it for core.dpdk.org (see the patch below). > > Looks good, thanks. > >> Thanks for the report. >> >> >>> And supported hardware information is presented in two different location in >>> webpage: >>> https://core.dpdk.org/supported/ >>> https://www.dpdk.org/ecosystem/#hardware >>> >>> Can we reduce it into single place? >>> Is ecosystem good place for listing hardware support? >> >> I think the intent of the ecosystem page was to show a diversity of vendors. >> I think we don't need all the details here. >> As it is more a technical DPDK info, I think it should be in core.dpdk.org. >> And it will be easier to update the device models regularly and precisely with patches. >> >> I suggest to limit the ecosystem page at vendor names, add CPU and other HW, >> and point to the core.dpdk.org page for details. > > +1 "https://www.dpdk.org/ecosystem/#hardware" is still there and XXV710 is still missing! What is the process of updating LF managed web pages? Is someone tracking this mail list? > >> >> >>> And as last, formatting of multiple device listing is not good, it is almost not >>> readable for Intel ones on https://core.dpdk.org/supported/, how can we fix it? >> >> Yes, this the format proposed in the first version drafted by the Linux Foundation. >> I have not changed it because I am not sure what is better. >> There is a nice page well formatted for each vendor when clicking on the name. >> Example: >> https://core.dpdk.org/supported/nics/intel/ > > Yes this page look better, I think it is better to have similar view in support > page. > >> >> >> --------------------- >> >> --- a/content/supported/NICs/intel.md >> +++ b/content/supported/NICs/intel.md >> @@ -10,7 +10,7 @@ weight = "7" >> - [e1000e](http://git.dpdk.org/dpdk/tree/drivers/net/e1000/) (82571, 82572, 82573, 82574, 82583, ICH8, ICH9, ICH10, PCH, PCH2, I217, I218, I219) >> - [igb](http://doc.dpdk.org/guides/nics/igb.html) (82575, 82576, 82580, I210, I211, I350, I354, DH89xx) >> - [ixgbe](http://doc.dpdk.org/guides/nics/ixgbe.html) (82598, 82599, X520, X540, X550) >> -- [i40e](http://doc.dpdk.org/guides/nics/i40e.html) (X710, XL710, X722) >> +- [i40e](http://doc.dpdk.org/guides/nics/i40e.html) (X710, XL710, X722, XXV710) >> - [fm10k](http://doc.dpdk.org/guides/nics/fm10k.html) (FM10420) >> >> {{% notice note %}} >> >> --- a/content/supported/NICs/marvell.md >> +++ b/content/supported/NICs/marvell.md >> @@ -6,4 +6,4 @@ type = "nic" >> weight = "8" >> +++ >> >> -- [mrvl](http://doc.dpdk.org/guides/nics/mvpp2.html) (Marvell Packet Processor v2) >> +- [mvpp2](http://doc.dpdk.org/guides/nics/mvpp2.html) (Marvell Packet Processor v2) >> >> --- a/content/supported/NICs/mellanox.md >> +++ b/content/supported/NICs/mellanox.md >> @@ -7,4 +7,4 @@ weight = "9" >> +++ >> >> - [mlx4](http://doc.dpdk.org/guides/nics/mlx4.html) (ConnectX-3, ConnectX-3 Pro) >> -- [mlx5](http://doc.dpdk.org/guides/nics/mlx5.html) (ConnectX-4, ConnectX-4 Lx, ConnectX-5) >> +- [mlx5](http://doc.dpdk.org/guides/nics/mlx5.html) (ConnectX-4, ConnectX-4 Lx, ConnectX-5, Bluefield) >> >> --- a/content/supported/NICs/solarflare.md >> +++ b/content/supported/NICs/solarflare.md >> @@ -6,4 +6,4 @@ type = "nic" >> weight = "13" >> +++ >> >> -- [sfc_efx](http://doc.dpdk.org/guides/nics/sfc_efx.html) (SFN7xxx, SFN8xxx) >> +- [sfc_efx](http://doc.dpdk.org/guides/nics/sfc_efx.html) (SFN7xxx, SFN8xxx, XtremeScale X2) >> >> >> >
Hi Ferruh, Thanks for your mail. The ecosystem page points to http://core.dpdk.org/supported/ which is the page of reference for the hardware. The ecosystem page is not meant to be exhaustive list and just a sample to show diversity of available hardware, the URLs point to the respective pages in core. Ie. Intel page goes to http://core.dpdk.org/supported/nics/intel/ . We will be simplifying the Ecosystem page in the future to make it clearer. Trishan On Tue, Aug 21, 2018 at 7:15 AM Ferruh Yigit <ferruh.yigit@intel.com> wrote: > On 7/2/2018 11:32 AM, Ferruh Yigit wrote: > > On 6/28/2018 9:11 PM, Thomas Monjalon wrote: > >> 28/06/2018 18:45, Ferruh Yigit: > >>> On 5/29/2018 9:00 AM, Thomas Monjalon wrote: > >>>> 29/05/2018 04:19, Wenzhuo Lu: > >>>>> From: Qiming Yang <qiming.yang@intel.com> > >>>>> > >>>>> XXV710 is pre-enabled on v16.11 and be validated on v17.02. > >>>>> > >>>>> Reference commit: 75d133dd32963c6897f97077c270082f1b4fef4e > >>>>> > >>>>> Signed-off-by: Qiming Yang <qiming.yang@intel.com> > >>>> > >>>> Applied, thanks > >>> > >>> Hi Thomas, > >>> > >>> I can't see this information (XXV710 as supported NIC) in the web > page, it may > >>> be lost somehow, how can we add it back? > >> > >> Yes it has been lost with other NICs recent update when migrating. > >> I have fixed it for core.dpdk.org (see the patch below). > > > > Looks good, thanks. > > > >> Thanks for the report. > >> > >> > >>> And supported hardware information is presented in two different > location in > >>> webpage: > >>> https://core.dpdk.org/supported/ > >>> https://www.dpdk.org/ecosystem/#hardware > >>> > >>> Can we reduce it into single place? > >>> Is ecosystem good place for listing hardware support? > >> > >> I think the intent of the ecosystem page was to show a diversity of > vendors. > >> I think we don't need all the details here. > >> As it is more a technical DPDK info, I think it should be in > core.dpdk.org. > >> And it will be easier to update the device models regularly and > precisely with patches. > >> > >> I suggest to limit the ecosystem page at vendor names, add CPU and > other HW, > >> and point to the core.dpdk.org page for details. > > > > +1 > > "https://www.dpdk.org/ecosystem/#hardware" is still there and XXV710 is > still > missing! > > What is the process of updating LF managed web pages? Is someone tracking > this > mail list? > > > > >> > >> > >>> And as last, formatting of multiple device listing is not good, it is > almost not > >>> readable for Intel ones on https://core.dpdk.org/supported/, how can > we fix it? > >> > >> Yes, this the format proposed in the first version drafted by the Linux > Foundation. > >> I have not changed it because I am not sure what is better. > >> There is a nice page well formatted for each vendor when clicking on > the name. > >> Example: > >> https://core.dpdk.org/supported/nics/intel/ > > > > Yes this page look better, I think it is better to have similar view in > support > > page. > > > >> > >> > >> --------------------- > >> > >> --- a/content/supported/NICs/intel.md > >> +++ b/content/supported/NICs/intel.md > >> @@ -10,7 +10,7 @@ weight = "7" > >> - [e1000e](http://git.dpdk.org/dpdk/tree/drivers/net/e1000/) (82571, > 82572, 82573, 82574, 82583, ICH8, ICH9, ICH10, PCH, PCH2, I217, I218, I219) > >> - [igb](http://doc.dpdk.org/guides/nics/igb.html) (82575, 82576, > 82580, I210, I211, I350, I354, DH89xx) > >> - [ixgbe](http://doc.dpdk.org/guides/nics/ixgbe.html) (82598, 82599, > X520, X540, X550) > >> -- [i40e](http://doc.dpdk.org/guides/nics/i40e.html) (X710, XL710, > X722) > >> +- [i40e](http://doc.dpdk.org/guides/nics/i40e.html) (X710, XL710, > X722, XXV710) > >> - [fm10k](http://doc.dpdk.org/guides/nics/fm10k.html) (FM10420) > >> > >> {{% notice note %}} > >> > >> --- a/content/supported/NICs/marvell.md > >> +++ b/content/supported/NICs/marvell.md > >> @@ -6,4 +6,4 @@ type = "nic" > >> weight = "8" > >> +++ > >> > >> -- [mrvl](http://doc.dpdk.org/guides/nics/mvpp2.html) (Marvell Packet > Processor v2) > >> +- [mvpp2](http://doc.dpdk.org/guides/nics/mvpp2.html) (Marvell Packet > Processor v2) > >> > >> --- a/content/supported/NICs/mellanox.md > >> +++ b/content/supported/NICs/mellanox.md > >> @@ -7,4 +7,4 @@ weight = "9" > >> +++ > >> > >> - [mlx4](http://doc.dpdk.org/guides/nics/mlx4.html) (ConnectX-3, > ConnectX-3 Pro) > >> -- [mlx5](http://doc.dpdk.org/guides/nics/mlx5.html) (ConnectX-4, > ConnectX-4 Lx, ConnectX-5) > >> +- [mlx5](http://doc.dpdk.org/guides/nics/mlx5.html) (ConnectX-4, > ConnectX-4 Lx, ConnectX-5, Bluefield) > >> > >> --- a/content/supported/NICs/solarflare.md > >> +++ b/content/supported/NICs/solarflare.md > >> @@ -6,4 +6,4 @@ type = "nic" > >> weight = "13" > >> +++ > >> > >> -- [sfc_efx](http://doc.dpdk.org/guides/nics/sfc_efx.html) (SFN7xxx, > SFN8xxx) > >> +- [sfc_efx](http://doc.dpdk.org/guides/nics/sfc_efx.html) (SFN7xxx, > SFN8xxx, XtremeScale X2) > >> > >> > >> > > > > -- Trishan R. de Lanerolle Program Manager, Networking Linux Foundation voice: +1.203.699.6401 skype: tdelanerolle email: tdelanerolle@linuxfoundation.org
On 8/21/2018 12:23 PM, Trishan de Lanerolle wrote: > Hi Ferruh, > Thanks for your mail. The ecosystem page points > to http://core.dpdk.org/supported/ which is the page of reference for the > hardware. The ecosystem page is not meant to be exhaustive list and just a > sample to show diversity of available hardware, the URLs point to the respective > pages in core. Ie. Intel page goes to http://core.dpdk.org/supported/nics/intel/ . > > We will be simplifying the Ecosystem page in the future to make it clearer. Hi Trishan, Thanks for the prompt response, as mentioned previously, I think it is better to remove duplication here and have a single page that list the supported hardware. Thanks, ferruh > > Trishan > > > On Tue, Aug 21, 2018 at 7:15 AM Ferruh Yigit <ferruh.yigit@intel.com > <mailto:ferruh.yigit@intel.com>> wrote: > > On 7/2/2018 11:32 AM, Ferruh Yigit wrote: > > On 6/28/2018 9:11 PM, Thomas Monjalon wrote: > >> 28/06/2018 18:45, Ferruh Yigit: > >>> On 5/29/2018 9:00 AM, Thomas Monjalon wrote: > >>>> 29/05/2018 04:19, Wenzhuo Lu: > >>>>> From: Qiming Yang <qiming.yang@intel.com <mailto:qiming.yang@intel.com>> > >>>>> > >>>>> XXV710 is pre-enabled on v16.11 and be validated on v17.02. > >>>>> > >>>>> Reference commit: 75d133dd32963c6897f97077c270082f1b4fef4e > >>>>> > >>>>> Signed-off-by: Qiming Yang <qiming.yang@intel.com > <mailto:qiming.yang@intel.com>> > >>>> > >>>> Applied, thanks > >>> > >>> Hi Thomas, > >>> > >>> I can't see this information (XXV710 as supported NIC) in the web page, > it may > >>> be lost somehow, how can we add it back? > >> > >> Yes it has been lost with other NICs recent update when migrating. > >> I have fixed it for core.dpdk.org <http://core.dpdk.org> (see the patch > below). > > > > Looks good, thanks. > > > >> Thanks for the report. > >> > >> > >>> And supported hardware information is presented in two different location in > >>> webpage: > >>> https://core.dpdk.org/supported/ > >>> https://www.dpdk.org/ecosystem/#hardware > >>> > >>> Can we reduce it into single place? > >>> Is ecosystem good place for listing hardware support? > >> > >> I think the intent of the ecosystem page was to show a diversity of vendors. > >> I think we don't need all the details here. > >> As it is more a technical DPDK info, I think it should be in > core.dpdk.org <http://core.dpdk.org>. > >> And it will be easier to update the device models regularly and precisely > with patches. > >> > >> I suggest to limit the ecosystem page at vendor names, add CPU and other HW, > >> and point to the core.dpdk.org <http://core.dpdk.org> page for details. > > > > +1 > > "https://www.dpdk.org/ecosystem/#hardware" is still there and XXV710 is still > missing! > > What is the process of updating LF managed web pages? Is someone tracking this > mail list? > > > > >> > >> > >>> And as last, formatting of multiple device listing is not good, it is > almost not > >>> readable for Intel ones on https://core.dpdk.org/supported/, how can we > fix it? > >> > >> Yes, this the format proposed in the first version drafted by the Linux > Foundation. > >> I have not changed it because I am not sure what is better. > >> There is a nice page well formatted for each vendor when clicking on the > name. > >> Example: > >> https://core.dpdk.org/supported/nics/intel/ > > > > Yes this page look better, I think it is better to have similar view in > support > > page. > > > >> > >> > >> --------------------- > >> > >> --- a/content/supported/NICs/intel.md > >> +++ b/content/supported/NICs/intel.md > >> @@ -10,7 +10,7 @@ weight = "7" > >> - [e1000e](http://git.dpdk.org/dpdk/tree/drivers/net/e1000/) (82571, > 82572, 82573, 82574, 82583, ICH8, ICH9, ICH10, PCH, PCH2, I217, I218, I219) > >> - [igb](http://doc.dpdk.org/guides/nics/igb.html) (82575, 82576, 82580, > I210, I211, I350, I354, DH89xx) > >> - [ixgbe](http://doc.dpdk.org/guides/nics/ixgbe.html) (82598, 82599, > X520, X540, X550) > >> -- [i40e](http://doc.dpdk.org/guides/nics/i40e.html) (X710, XL710, X722) > >> +- [i40e](http://doc.dpdk.org/guides/nics/i40e.html) (X710, XL710, X722, > XXV710) > >> - [fm10k](http://doc.dpdk.org/guides/nics/fm10k.html) (FM10420) > >> > >> {{% notice note %}} > >> > >> --- a/content/supported/NICs/marvell.md > >> +++ b/content/supported/NICs/marvell.md > >> @@ -6,4 +6,4 @@ type = "nic" > >> weight = "8" > >> +++ > >> > >> -- [mrvl](http://doc.dpdk.org/guides/nics/mvpp2.html) (Marvell Packet > Processor v2) > >> +- [mvpp2](http://doc.dpdk.org/guides/nics/mvpp2.html) (Marvell Packet > Processor v2) > >> > >> --- a/content/supported/NICs/mellanox.md > >> +++ b/content/supported/NICs/mellanox.md > >> @@ -7,4 +7,4 @@ weight = "9" > >> +++ > >> > >> - [mlx4](http://doc.dpdk.org/guides/nics/mlx4.html) (ConnectX-3, > ConnectX-3 Pro) > >> -- [mlx5](http://doc.dpdk.org/guides/nics/mlx5.html) (ConnectX-4, > ConnectX-4 Lx, ConnectX-5) > >> +- [mlx5](http://doc.dpdk.org/guides/nics/mlx5.html) (ConnectX-4, > ConnectX-4 Lx, ConnectX-5, Bluefield) > >> > >> --- a/content/supported/NICs/solarflare.md > >> +++ b/content/supported/NICs/solarflare.md > >> @@ -6,4 +6,4 @@ type = "nic" > >> weight = "13" > >> +++ > >> > >> -- [sfc_efx](http://doc.dpdk.org/guides/nics/sfc_efx.html) (SFN7xxx, SFN8xxx) > >> +- [sfc_efx](http://doc.dpdk.org/guides/nics/sfc_efx.html) (SFN7xxx, > SFN8xxx, XtremeScale X2) > >> > >> > >> > > > > > > -- > Trishan R. de Lanerolle > Program Manager, Networking > Linux Foundation > voice: +1.203.699.6401 > skype: tdelanerolle > email: tdelanerolle@linuxfoundation.org <mailto:tdelanerolle@linuxfoundation.org>
On 8/21/2018 12:31 PM, Ferruh Yigit wrote: > On 8/21/2018 12:23 PM, Trishan de Lanerolle wrote: >> Hi Ferruh, >> Thanks for your mail. The ecosystem page points >> to http://core.dpdk.org/supported/ which is the page of reference for the >> hardware. The ecosystem page is not meant to be exhaustive list and just a >> sample to show diversity of available hardware, the URLs point to the respective >> pages in core. Ie. Intel page goes to http://core.dpdk.org/supported/nics/intel/ . >> >> We will be simplifying the Ecosystem page in the future to make it clearer. > > Hi Trishan, > > Thanks for the prompt response, as mentioned previously, I think it is better to > remove duplication here and have a single page that list the supported hardware. Hi Trishan, I have just recognized ecosystem-supported_hardware [1] has been updated, I think looks better now, thanks. [1]: https://www.dpdk.org/ecosystem/#hardware