DPDK website maintenance
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: web@dpdk.org, Wenzhuo Lu <wenzhuo.lu@intel.com>,
	Qiming Yang <qiming.yang@intel.com>,
	Trishan de Lanerolle <tdelanerolle@linuxfoundation.org>
Subject: Re: [dpdk-web] supported hardware list
Date: Mon, 2 Jul 2018 11:32:42 +0100	[thread overview]
Message-ID: <13da655b-b0cc-9790-24b9-510c2958b122@intel.com> (raw)
In-Reply-To: <9809937.ZzNijnmssY@xps>

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)
> 
> 
> 

  reply	other threads:[~2018-07-02 10:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-16  2:32 [dpdk-web] [PATCH] add XXV710 to i40e suppported NICs Wenzhuo Lu
2018-05-16  5:50 ` Zhang, Helin
2018-05-16  8:26 ` Mcnamara, John
2018-05-17 13:20 ` Thomas Monjalon
2018-05-29  2:19 ` [dpdk-web] [PATCH v2] " Wenzhuo Lu
2018-05-29  8:00   ` Thomas Monjalon
2018-06-28 16:45     ` Ferruh Yigit
2018-06-28 20:11       ` [dpdk-web] supported hardware list Thomas Monjalon
2018-07-02 10:32         ` Ferruh Yigit [this message]
2018-08-21 11:15           ` Ferruh Yigit
2018-08-21 11:23             ` Trishan de Lanerolle
2018-08-21 11:31               ` Ferruh Yigit
2018-09-03  7:56                 ` 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=13da655b-b0cc-9790-24b9-510c2958b122@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=qiming.yang@intel.com \
    --cc=tdelanerolle@linuxfoundation.org \
    --cc=thomas@monjalon.net \
    --cc=web@dpdk.org \
    --cc=wenzhuo.lu@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).