From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Trishan de Lanerolle <tdelanerolle@linuxfoundation.org>
Cc: Thomas Monjalon <thomas@monjalon.net>,
web@dpdk.org, wenzhuo.lu@intel.com, qiming.yang@intel.com,
Jill Lovato <jlovato@linuxfoundation.org>
Subject: Re: [dpdk-web] supported hardware list
Date: Mon, 3 Sep 2018 08:56:22 +0100 [thread overview]
Message-ID: <10d7f5b7-fbff-ca9f-de4e-901f72e5f2f1@intel.com> (raw)
In-Reply-To: <91e50dba-29a2-b2b9-0f2c-8566072f3ff9@intel.com>
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
prev parent reply other threads:[~2018-09-03 7:56 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
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 [this message]
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=10d7f5b7-fbff-ca9f-de4e-901f72e5f2f1@intel.com \
--to=ferruh.yigit@intel.com \
--cc=jlovato@linuxfoundation.org \
--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).