From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Shahaf Shuler <shahafs@mellanox.com>,
nelio.laranjeiro@6wind.com, adrien.mazarguil@6wind.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 1/1] net/mlx5: add hardware TSO support
Date: Mon, 6 Mar 2017 08:50:01 +0000 [thread overview]
Message-ID: <8379d78f-4448-f6b3-0f24-5ab23561a3af@intel.com> (raw)
In-Reply-To: <1488445291-24637-1-git-send-email-shahafs@mellanox.com>
On 3/2/2017 9:01 AM, Shahaf Shuler wrote:
> Implement support for hardware TSO.
>
> Signed-off-by: Shahaf Shuler <shahafs@mellanox.com>
> ---
> on v3:
> * fix alignment issues
> * for warn log
> on v2:
> * Instead of exposing capability, TSO checks on data path.
> * PMD specific parameter to enable TSO.
> * different implementaion for the data path.
> Performance impact ~0.1-0.2Mpps
Hi Shahaf,
I think it is good idea to update release notes to announce mlx5 TSO
support, what do you think?
And if you will send a new version of the patch, can you please put
"TSO" flag in the same order with default.ini
Thanks,
ferruh
next prev parent reply other threads:[~2017-03-06 8:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 16:09 [dpdk-dev] [PATCH 0/4] net/mlx5 add " Shahaf Shuler
2017-02-22 16:09 ` [dpdk-dev] [PATCH 1/4] ethdev: add Tx offload limitations Shahaf Shuler
2017-02-22 16:09 ` [dpdk-dev] [PATCH 2/4] ethdev: add TSO disable flag Shahaf Shuler
2017-02-22 16:09 ` [dpdk-dev] [PATCH 3/4] app/testpmd: add TSO disable to test options Shahaf Shuler
2017-02-22 16:10 ` [dpdk-dev] [PATCH 4/4] net/mlx5: add hardware TSO support Shahaf Shuler
2017-03-01 11:11 ` [dpdk-dev] [PATCH v2 0/1] net/mlx5: add " Shahaf Shuler
2017-03-01 11:11 ` [dpdk-dev] [PATCH v2 1/1] net/mlx5: add hardware " Shahaf Shuler
2017-03-01 14:33 ` Nélio Laranjeiro
2017-03-02 9:01 ` [dpdk-dev] [PATCH v3 " Shahaf Shuler
2017-03-02 9:15 ` Nélio Laranjeiro
2017-03-06 9:32 ` Ferruh Yigit
2017-03-06 8:50 ` Ferruh Yigit [this message]
2017-03-06 9:31 ` Ferruh Yigit
2017-03-06 11:03 ` 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=8379d78f-4448-f6b3-0f24-5ab23561a3af@intel.com \
--to=ferruh.yigit@intel.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=nelio.laranjeiro@6wind.com \
--cc=shahafs@mellanox.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).