DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Gaëtan Rivet" <gaetan.rivet@6wind.com>
To: Ophir Munk <ophirmu@mellanox.com>
Cc: dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>,
	Olga Shern <olgas@mellanox.com>,
	Pascal Mazon <pascal.mazon@6wind.com>
Subject: Re: [dpdk-dev] [PATCH v1] net/failsafe: add TCP TSO default Tx capability
Date: Tue, 24 Apr 2018 15:11:17 +0200	[thread overview]
Message-ID: <20180424131117.zilfv6cqddd6ztvz@bidouze.vm.6wind.com> (raw)
In-Reply-To: <1523341020-4534-1-git-send-email-ophirmu@mellanox.com>

Hi Ophir,

On Tue, Apr 10, 2018 at 06:17:00AM +0000, Ophir Munk wrote:
> Add DEV_TX_OFFLOAD_TCP_TSO to failsafe Tx offload default capabilities.
> The net result of failsafe Tx capabilities is the logical AND of Tx
> capabilities among all failsafe sub_devices and failsafe own default
> capabilities.
> 
> Signed-off-by: Ophir Munk <ophirmu@mellanox.com>

Acked-by: Gaetan Rivet <gaetan.rivet@6wind.com>

> ---
>  drivers/net/failsafe/failsafe_ops.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/net/failsafe/failsafe_ops.c b/drivers/net/failsafe/failsafe_ops.c
> index 057e435..e33821a 100644
> --- a/drivers/net/failsafe/failsafe_ops.c
> +++ b/drivers/net/failsafe/failsafe_ops.c
> @@ -81,7 +81,8 @@ static struct rte_eth_dev_info default_infos = {
>  		DEV_TX_OFFLOAD_MULTI_SEGS |
>  		DEV_TX_OFFLOAD_IPV4_CKSUM |
>  		DEV_TX_OFFLOAD_UDP_CKSUM |
> -		DEV_TX_OFFLOAD_TCP_CKSUM,
> +		DEV_TX_OFFLOAD_TCP_CKSUM |
> +		DEV_TX_OFFLOAD_TCP_TSO,
>  	.flow_type_rss_offloads = 0x0,
>  };
>  
> -- 
> 2.7.4
> 

Thanks,
-- 
Gaëtan Rivet
6WIND

  parent reply	other threads:[~2018-04-24 13:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-10  6:17 Ophir Munk
2018-04-24 12:49 ` Ferruh Yigit
2018-04-24 13:11 ` Gaëtan Rivet [this message]
2018-04-24 14:17   ` Ferruh Yigit
2018-04-24 14:19     ` Gaëtan Rivet

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=20180424131117.zilfv6cqddd6ztvz@bidouze.vm.6wind.com \
    --to=gaetan.rivet@6wind.com \
    --cc=dev@dpdk.org \
    --cc=olgas@mellanox.com \
    --cc=ophirmu@mellanox.com \
    --cc=pascal.mazon@6wind.com \
    --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).