DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shahaf Shuler <shahafs@mellanox.com>
To: thomas@monjalon.net
Cc: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v3 1/3] doc: update mlx5 supported features
Date: Wed, 26 Jul 2017 09:48:41 +0300	[thread overview]
Message-ID: <50a96ef776aa322a707a558e01b46920f273fa99.1501051600.git.shahafs@mellanox.com> (raw)
In-Reply-To: <e2228d8e47cac18d977b991247c0f11454198db0.1500984274.git.shahafs@mellanox.com>

Supported features which were not included:
  * ARMv8
  * Extended stats

Not supported features which were wrongly included:
  * Inner L3 checksum
  * Inner L4 checksum

Signed-off-by: Shahaf Shuler <shahafs@mellanox.com>
Acked-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
Acked-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
---
 doc/guides/nics/features/mlx5.ini | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/guides/nics/features/mlx5.ini b/doc/guides/nics/features/mlx5.ini
index e228c4126..2913591c9 100644
--- a/doc/guides/nics/features/mlx5.ini
+++ b/doc/guides/nics/features/mlx5.ini
@@ -28,15 +28,15 @@ CRC offload          = Y
 VLAN offload         = Y
 L3 checksum offload  = Y
 L4 checksum offload  = Y
-Inner L3 checksum    = Y
-Inner L4 checksum    = Y
 Packet type parsing  = Y
 Rx descriptor status = Y
 Tx descriptor status = Y
 Basic stats          = Y
+Extended stats       = Y
 Stats per queue      = Y
 Multiprocess aware   = Y
 Other kdrv           = Y
+ARMv8                = Y
 Power8               = Y
 x86-32               = Y
 x86-64               = Y
-- 
2.12.0

  reply	other threads:[~2017-07-26  6:48 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-24 12:36 [dpdk-dev] [PATCH " Shahaf Shuler
2017-07-24 12:36 ` [dpdk-dev] [PATCH 2/3] doc: update release notes for mlx driver Shahaf Shuler
2017-07-24 12:36 ` [dpdk-dev] [PATCH 3/3] doc: update mlx guides Shahaf Shuler
     [not found]   ` <20170725071639.GJ19852@6wind.com>
2017-07-25 11:52     ` Shahaf Shuler
2017-07-25 12:07 ` [dpdk-dev] [PATCH v2 1/3] doc: update mlx5 supported features Shahaf Shuler
2017-07-26  6:48   ` Shahaf Shuler [this message]
2017-07-26 17:02     ` [dpdk-dev] [PATCH v4 " Shahaf Shuler
2017-07-28 11:56       ` Mcnamara, John
2017-07-28 14:28       ` [dpdk-dev] [PATCH v5 " Shahaf Shuler
2017-07-28 14:28       ` [dpdk-dev] [PATCH v5 2/3] doc: update release notes for mlx driver Shahaf Shuler
2017-07-28 14:28       ` [dpdk-dev] [PATCH v5 3/3] doc: update mlx guides Shahaf Shuler
2017-07-31 11:26         ` Mcnamara, John
2017-07-31 21:53           ` Thomas Monjalon
2017-07-26 17:02     ` [dpdk-dev] [PATCH v4 2/3] doc: update release notes for mlx driver Shahaf Shuler
2017-07-28 11:57       ` Mcnamara, John
2017-07-26 17:02     ` [dpdk-dev] [PATCH v4 3/3] doc: update mlx guides Shahaf Shuler
2017-07-28 12:07       ` Mcnamara, John
2017-07-26  6:48   ` [dpdk-dev] [PATCH v3 2/3] doc: update release notes for mlx driver Shahaf Shuler
2017-07-26  6:48   ` [dpdk-dev] [PATCH v3 3/3] doc: update mlx guides Shahaf Shuler
2017-07-25 12:07 ` [dpdk-dev] [PATCH v2 2/3] doc: update release notes for mlx driver Shahaf Shuler
2017-07-25 12:07 ` [dpdk-dev] [PATCH v2 3/3] doc: update mlx guides Shahaf Shuler

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=50a96ef776aa322a707a558e01b46920f273fa99.1501051600.git.shahafs@mellanox.com \
    --to=shahafs@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).