From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: "Tan, Jianfeng" <jianfeng.tan@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] doc: fill nics features matrix for mlx4 & mlx5
Date: Thu, 31 Mar 2016 13:00:54 +0200 [thread overview]
Message-ID: <20160331110054.GN27079@6wind.com> (raw)
In-Reply-To: <56FD022D.8050406@intel.com>
On Thu, Mar 31, 2016 at 06:55:41PM +0800, Tan, Jianfeng wrote:
> Hi,
>
> On 3/31/2016 6:22 PM, Adrien Mazarguil wrote:
> >Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
> >---
> > doc/guides/nics/overview.rst | 56 ++++++++++++++++++++++----------------------
> > 1 file changed, 28 insertions(+), 28 deletions(-)
> >
> >diff --git a/doc/guides/nics/overview.rst b/doc/guides/nics/overview.rst
> >index 542479a..5238088 100644
> >--- a/doc/guides/nics/overview.rst
> >+++ b/doc/guides/nics/overview.rst
> >@@ -86,63 +86,63 @@ Most of these differences are summarized below.
> > e e e e e e
> > c c c c c c
> > ==================== = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> >- link status X X X X X
> >- link status event X X X
> >+ link status X X X X X X X
> >+ link status event X X X X X
> > queue status event X
> > Rx interrupt X X X X
> >- queue start/stop X X X X X X X
> >- MTU update X X
> >- jumbo frame X X X X X X
> >- scattered Rx X X X X X X X
> >+ queue start/stop X X X X X X X X X
> >+ MTU update X X X X
> >+ jumbo frame X X X X X X X X
> >+ scattered Rx X X X X X X X X X
> > LRO
> > TSO X X X X X X
> >- promiscuous mode X X X X X X
> >- allmulticast mode X X X X X X
> >+ promiscuous mode X X X X X X X X
> >+ allmulticast mode X X X X X X X X
> > unicast MAC filter X X X X
> > multicast MAC filter X X X X
> >- RSS hash X X X X X X
> >- RSS key update X X X X X
> >- RSS reta update X X X X X
> >+ RSS hash X X X X X X X X
> >+ RSS key update X X X X X X
> >+ RSS reta update X X X X X X
> > VMDq X X
> >- SR-IOV X X X
> >+ SR-IOV X X X X X
> > DCB X X
> >- VLAN filter X X X X
> >+ VLAN filter X X X X X X
> > ethertype filter X X
> > n-tuple filter
> > SYN filter
> > tunnel filter X X
> > flexible filter
> > hash filter X X X X
> >- flow director X X
> >+ flow director X X X
> > flow control X X X
> > rate limitation
> > traffic mirroring X X
> >- CRC offload X X X X
> >- VLAN offload X X X X
> >+ CRC offload X X X X X
> >+ VLAN offload X X X X X
> > QinQ offload X X
> >- L3 checksum offload X X X X
> >- L4 checksum offload X X X X
> >- inner L3 checksum X X X
> >- inner L4 checksum X X X
> >- packet type parsing X X X
> >+ L3 checksum offload X X X X X X
> >+ L4 checksum offload X X X X X X
> >+ inner L3 checksum X X X X
> >+ inner L4 checksum X X X X
> >+ packet type parsing X X X X X
> > timesync X X
> >- basic stats X X X X X X X X
> >+ basic stats X X X X X X X X X X
> > extended stats X X X X X
> >- stats per queue X X
> >+ stats per queue X X X X
> > EEPROM dump
> > registers dump
> >- multiprocess aware X X X X
> >+ multiprocess aware X X X X X X
> > BSD nic_uio X X X X X
> > Linux UIO X X X X X X
> > Linux VFIO X X X X X
> > other kdrv X
> > ARMv7
> > ARMv8
> >- Power8
> >+ Power8 X X
> > TILE-Gx
> >- x86-32 X X X X X X X
> >- x86-64 X X X X X X X X
> >- usage doc X X
> >+ x86-32 X X X X X X X X X
> >+ x86-64 X X X X X X X X X X
> >+ usage doc X X X X
> > design doc
> > perf doc
> > ==================== = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
>
> Here "X" means "support"?
Erm, I must say I did not consider it could mean something else, I guess it
does?
Perhaps a few features could use a character other than "X" when additional
details are necessary (for instance incomplete features).
--
Adrien Mazarguil
6WIND
next prev parent reply other threads:[~2016-03-31 11:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 10:22 Adrien Mazarguil
2016-03-31 10:55 ` Tan, Jianfeng
2016-03-31 11:00 ` Adrien Mazarguil [this message]
2016-03-31 12:50 ` Tan, Jianfeng
2016-03-31 12:55 ` Thomas Monjalon
2016-04-01 21:47 ` 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=20160331110054.GN27079@6wind.com \
--to=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=jianfeng.tan@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).