DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Matan Azrad <matan@mellanox.com>, Tiwei Bie <tiwei.bie@intel.com>
Cc: Noa Ezra <noae@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/2] net/vhost: support TSO disabling
Date: Thu, 20 Jun 2019 09:25:17 +0200	[thread overview]
Message-ID: <eeacb576-2151-b270-bb46-d17b4a1210de@redhat.com> (raw)
In-Reply-To: <AM0PR0502MB401924A5720889C11F45447BD2E40@AM0PR0502MB4019.eurprd05.prod.outlook.com>



On 6/20/19 8:08 AM, Matan Azrad wrote:
> 
> 
> Hi Tiwei, Maxim
> From: Tiwei Bie
>> Sent: Thursday, June 20, 2019 5:26 AM
>> To: Maxime Coquelin <maxime.coquelin@redhat.com>
>> Cc: Noa Ezra <noae@mellanox.com>; Matan Azrad <matan@mellanox.com>;
>> dev@dpdk.org
>> Subject: Re: [PATCH 1/2] net/vhost: support TSO disabling
>>
>> On Wed, Jun 19, 2019 at 11:53:05AM +0200, Maxime Coquelin wrote:
>>> On 6/19/19 8:13 AM, Noa Ezra wrote:
>>>> TSO (TCP Segmentation Offload) is enabled by default on vhost.
>>>> Add the ability to disable TSO on vhost.
>>>> The user should also disable the feature on the virtual machine's xml.
>>>
>>> For TSO, I think it make sense to have the option to disable it, as it
>>> requires the application to support it.
>>>
>>> I even wonder whether it should not be disabled by default.
>>> Any thoughts?
>>
>> Agree, it looks better to disable it by default.
> 
> The issue to disable it by default is that it will break the current applications/users which use TSO by default.
> 
> Maybe we need kind of notice to the user to break it in the next version.
> 
> What do you think?


I think that's a good idea, let's add a notice in the release note for
v19.08, and disable it by default in 19.11.

Thanks,
Maxime

>> Thanks,
>> Tiwei

  reply	other threads:[~2019-06-20  7:25 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-19  6:13 [dpdk-dev] [PATCH 0/2] support tso and mrg-rxbuf disabling Noa Ezra
2019-06-19  6:13 ` [dpdk-dev] [PATCH 1/2] net/vhost: support TSO disabling Noa Ezra
2019-06-19  9:53   ` Maxime Coquelin
2019-06-20  2:26     ` Tiwei Bie
2019-06-20  6:08       ` Matan Azrad
2019-06-20  7:25         ` Maxime Coquelin [this message]
2019-08-30  8:44   ` Maxime Coquelin
2019-09-30  9:02   ` Maxime Coquelin
2019-06-19  6:13 ` [dpdk-dev] [PATCH 2/2] net/vhost: support mrg-rxbuf disabling Noa Ezra
2019-06-19  9:10   ` Maxime Coquelin
2019-06-20  5:57     ` Noa Ezra
2019-06-20  6:52       ` Matan Azrad
2019-06-20  7:19         ` Maxime Coquelin
2019-06-20  7:55           ` Matan Azrad
2019-06-26  7:50             ` Matan Azrad
2019-06-26 10:27               ` Maxime Coquelin
2019-06-26 11:18                 ` Matan Azrad
2019-06-26 12:05                   ` Maxime Coquelin
2019-06-26 13:24                     ` Matan Azrad
2019-06-26 14:17                       ` Maxime Coquelin
2019-06-27  5:04                         ` Matan Azrad
2019-08-30  8:48                           ` Maxime Coquelin
2019-06-20  7:27       ` Maxime Coquelin
2019-09-30  9:04   ` Maxime Coquelin
2019-06-19 14:20 ` [dpdk-dev] [PATCH 0/2] support tso and " Aaron Conole

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=eeacb576-2151-b270-bb46-d17b4a1210de@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=dev@dpdk.org \
    --cc=matan@mellanox.com \
    --cc=noae@mellanox.com \
    --cc=tiwei.bie@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).