From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id DB7F71B4F0 for ; Thu, 28 Jun 2018 22:11:24 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 60A1621DC6; Thu, 28 Jun 2018 16:11:24 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Thu, 28 Jun 2018 16:11:24 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=3azNTpaRvYAVnY0ayEtXhGJTcY +jlcUO5mNx9/BY3y8=; b=mutbZNBCmX4A2lC/c7wQ7DNCJAFSwawyxHP2JFuCHu RPvpwhoP+rkPSxHgprMnPZ6/np06fqjj6FLikWiWQJq8ChVoRe+hamzsbefV7p2C eBpjyUlYpdyoiwZ+o/BieBOWz+5MoRFrg8jAUVFMqkPQ9E9wOLobrvKkQOu9FAN8 g= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=3azNTp aRvYAVnY0ayEtXhGJTcY+jlcUO5mNx9/BY3y8=; b=wivxdWp64hpuckLMp7Avv0 Mqr5uiAChuK1l6pgq2u9/NJ2dT/2dTzP4rRb6en62Hlr5oP/hIQRRkbZ+mN4pshT LZwEqZeBhUZ3YlE+6gjQsGOF2rUXUJW/vRHKCGgy+5BMXHjwVC8Rjw1ePrSG8TJW /NoRzoTGYrOeeRu/1LlDuYsP2nCuXQpC+BcobigMqBOWWbPgx2ttZp/u6DFSfVY8 BEn5tS019gPVBVqSk5mKjcEPh70CDYqHIQRi0RPS3GOQq+qFD/qzQ6wENcd1x51i +Yp1u3ciaO00tjZgaHvwug9ydLIasjD5Y5dIROv48+3m3w9eWoDIxmzI3LIrXt/g == X-ME-Proxy: X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 834FE10268; Thu, 28 Jun 2018 16:11:20 -0400 (EDT) From: Thomas Monjalon To: Ferruh Yigit Cc: web@dpdk.org, Wenzhuo Lu , Qiming Yang , Trishan de Lanerolle Date: Thu, 28 Jun 2018 22:11:19 +0200 Message-ID: <9809937.ZzNijnmssY@xps> In-Reply-To: References: <1526437942-3876-1-git-send-email-wenzhuo.lu@intel.com> <3194454.J7243SyqOs@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-web] supported hardware list X-BeenThere: web@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK website maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jun 2018 20:11:25 -0000 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 > >> > >> XXV710 is pre-enabled on v16.11 and be validated on v17.02. > >> > >> Reference commit: 75d133dd32963c6897f97077c270082f1b4fef4e > >> > >> Signed-off-by: Qiming Yang > > > > 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)