From: Trishan de Lanerolle <tdelanerolle@linuxfoundation.org>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>
Cc: web@dpdk.org, Thomas Monjalon <thomas@monjalon.net>,
Jill Lovato <jlovato@linuxfoundation.org>
Subject: Re: [dpdk-web] DPDK ecosystem gets out dated
Date: Tue, 27 Nov 2018 10:37:04 -0500 [thread overview]
Message-ID: <CAFXL6f_hQXaCm8T4BytL+HvQEo0ia+mThnBGSk1S+DBmpmCZdg@mail.gmail.com> (raw)
In-Reply-To: <e18ec9d1-cd6b-de36-f5cc-e0e8ad75f75e@intel.com>
Hi Ferruh,
The page was updated, we removed all references to specific hardware and
just link to the companies and core.dpdk.org/supported pages from the
ecosystem page.
The supported drivers page goes to the
http://doc.dpdk.org/guides/nics/overview.html page. We wanted to leave the
list of features to show the rich diversity of features available. We can
review that list for new features and add them in. The Ecosystem page is
not meant to be the page of reference, simply a highlights reel or
showcase.
Regards,
Trishan
On Tue, Nov 27, 2018 at 10:10 AM Ferruh Yigit <ferruh.yigit@intel.com>
wrote:
> DPDK ecosystem page, https://www.dpdk.org/ecosystem/, sections
> - Supported Hardware
> - Supported Drivers
>
> gets outdated as code forwards.
>
> The "http://core.dpdk.org/supported/" is more up to date as a result of
> active
> effort there.
>
> We should either remove the duplication completely and link to
> http://core.dpdk.org/supported/ one, or someone should follow and reflect
> changes to https://www.dpdk.org/ecosystem/ .
>
> Thanks,
> ferruh
>
--
Trishan R. de Lanerolle
Program Manager, Networking
Linux Foundation
voice: +1.203.699.6401
skype: tdelanerolle
email: tdelanerolle@linuxfoundation.org
next prev parent reply other threads:[~2018-11-27 15:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 15:10 Ferruh Yigit
2018-11-27 15:37 ` Trishan de Lanerolle [this message]
2018-11-27 16:11 ` Ferruh Yigit
2018-11-27 16:17 ` Trishan de Lanerolle
2018-11-28 19:52 ` Stephen Hemminger
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=CAFXL6f_hQXaCm8T4BytL+HvQEo0ia+mThnBGSk1S+DBmpmCZdg@mail.gmail.com \
--to=tdelanerolle@linuxfoundation.org \
--cc=ferruh.yigit@intel.com \
--cc=jlovato@linuxfoundation.org \
--cc=thomas@monjalon.net \
--cc=web@dpdk.org \
/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).