From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: rahul.lakkireddy@chelsio.com, qi.z.zhang@intel.com,
xiao.w.wang@intel.com, xavier.huwei@huawei.com,
beilei.xing@intel.com, wenzhuo.lu@intel.com,
qiming.yang@intel.com, konstantin.ananyev@intel.com,
ferruh.yigit@intel.com, jerinj@marvell.com, rmody@marvell.com,
shshaikh@marvell.com, maxime.coquelin@redhat.com,
xiaolong.ye@intel.com
Subject: Re: [dpdk-dev] [PATCH 0/3] refresh NIC features matrix
Date: Wed, 18 Mar 2020 12:42:14 +0100 [thread overview]
Message-ID: <3077860.AxlXzFCzgd@xps> (raw)
In-Reply-To: <20200311230136.63452-1-thomas@monjalon.net>
Ping for review and action on follow-up patches please.
I hope we won't have to block patches to get things done.
Ferruh, I think we need an action plan.
12/03/2020 00:01, Thomas Monjalon:
> This series aims to clean-up the big table of ethdev features:
> http://doc.dpdk.org/guides/nics/overview.html#id1
>
> We could reorganize the information in this table,
> maybe split it or add/remove some rows.
> Before going to such reorganization, we should clean it up.
>
> The first patch is fixing the look & size of the table with recent sphinx.
>
> The second and third patches are removing 8 columns which are
> clearly unneeded:
> - bnx2x_vf
> - bonding
> - kni
> - nfp_vf
> - null
> - ring
> - softnic
> - vdev_netvsc
>
> More columns can be removed by merging PF/VF and vector datapaths.
> If a feature cannot be supported in all cases, it should be marked
> as partially supported (P).
> If a feature is PF-specific (like flow control), that's OK to mark
> it fully supported because it's obviously impossible for VF.
> There are also some features which were probably marked in some
> columns and missed in its VF or vector counterpart.
> Please work to merge and drop these 16 columns:
> - cxgbevf
> - fm10k_vf
> - hns3_vf
> - i40e_vec
> - i40e_vf
> - i40e_vf_vec
> - iavf_vec
> - ice_vec
> - igb_vf
> - ixgbe_vec
> - ixgbe_vf
> - ixgbe_vf_vec
> - octeontx2_vec
> - octeontx2_vf
> - qede_vf
> - virtio_vec
>
> The total gain is to reduce the table size from 71 to 47 columns.
>
> Please send patches for Chelsio, Huawei, Intel, Marvell and virtio.
next prev parent reply other threads:[~2020-03-18 11:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 23:01 [dpdk-dev] [PATCH 0/3] refresh NIC features matrix Thomas Monjalon
2020-03-11 23:01 ` [dpdk-dev] [PATCH 1/3] doc: fix matrix CSS for recent sphinx Thomas Monjalon
2020-03-11 23:01 ` [dpdk-dev] [PATCH 2/3] doc: remove empty columns from NIC features matrix Thomas Monjalon
2020-03-11 23:01 ` [dpdk-dev] [PATCH 3/3] doc: remove similar " Thomas Monjalon
2020-03-18 11:42 ` Thomas Monjalon [this message]
2020-03-20 5:35 ` [dpdk-dev] [PATCH 0/3] refresh " Zhang, Qi Z
2020-03-20 10:44 ` Thomas Monjalon
2020-03-20 11:15 ` Zhang, Qi Z
2020-03-24 8:36 ` Andrew Rybchenko
2020-04-16 20:13 ` Thomas Monjalon
2020-04-17 16:32 ` Thomas Monjalon
2020-04-17 18:21 ` Ajit Khaparde
2020-04-16 21:57 ` Thomas Monjalon
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=3077860.AxlXzFCzgd@xps \
--to=thomas@monjalon.net \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.com \
--cc=konstantin.ananyev@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@intel.com \
--cc=rahul.lakkireddy@chelsio.com \
--cc=rmody@marvell.com \
--cc=shshaikh@marvell.com \
--cc=wenzhuo.lu@intel.com \
--cc=xavier.huwei@huawei.com \
--cc=xiao.w.wang@intel.com \
--cc=xiaolong.ye@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.