DPDK patches and discussions
 help / color / mirror / Atom feed
From: Elad Persiko <eladpe@mellanox.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] doc: add tso capabilities feature for mlx5
Date: Tue, 10 Jan 2017 09:18:37 +0000	[thread overview]
Message-ID: <HE1PR0501MB2473D194ADE0BD539B3796D1BC670@HE1PR0501MB2473.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <3c5731c6-4213-c976-9a17-798eb24d2c37@intel.com>


Thanks,
The feature is not supported on MLX4. I will fix it on V2

-----Original Message-----
From: Ferruh Yigit [mailto:ferruh.yigit@intel.com]
Sent: Monday, January 9, 2017 2:31 PM
To: Elad Persiko <eladpe@mellanox.com>; dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] doc: add tso capabilities feature for mlx5

On 1/8/2017 4:23 PM, Elad Persiko wrote:
> Feature implemented at:
> commit b007e98ccda9 ("net/mlx5: implement TSO data path") commit 
> 085c4137280a ("net/mlx5: support TSO in control plane")
> 
> Signed-off-by: Elad Persiko <eladpe@mellanox.com>
> ---
>  doc/guides/nics/features/mlx4.ini | 1 + 
> doc/guides/nics/features/mlx5.ini | 1 +
>  2 files changed, 2 insertions(+)
> 
> diff --git a/doc/guides/nics/features/mlx4.ini
> b/doc/guides/nics/features/mlx4.ini
> index c9828f7..d74b9dd 100644
> --- a/doc/guides/nics/features/mlx4.ini
> +++ b/doc/guides/nics/features/mlx4.ini
> @@ -10,6 +10,7 @@ Queue start/stop     = Y
>  MTU update           = Y
>  Jumbo frame          = Y
>  Scattered Rx         = Y
> +TSO                  = Y

One more thing, for double check, patch updates only mlx5 files, is enabling TSO for mlx4 correct?

>  Promiscuous mode     = Y
>  Allmulticast mode    = Y
>  Unicast MAC filter   = Y
<...>

  reply	other threads:[~2017-01-10  9:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-08 16:23 Elad Persiko
2017-01-09 10:52 ` Ferruh Yigit
2017-01-09 12:31 ` Ferruh Yigit
2017-01-10  9:18   ` Elad Persiko [this message]
2017-01-23 12:29     ` Ferruh Yigit
2017-01-23 12:38       ` Olga Shern

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=HE1PR0501MB2473D194ADE0BD539B3796D1BC670@HE1PR0501MB2473.eurprd05.prod.outlook.com \
    --to=eladpe@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@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).