DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: David Marchand <david.marchand@redhat.com>, dev@dpdk.org
Cc: thomas@monjalon.net, ferruh.yigit@intel.com,
	Chenbo Xia <chenbo.xia@intel.com>
Subject: Re: [dpdk-dev] [PATCH] net/vhost: restore pseudo TSO support
Date: Tue, 18 May 2021 09:16:52 +0200	[thread overview]
Message-ID: <d302e730-be90-ed36-c221-67153456be57@redhat.com> (raw)
In-Reply-To: <20210518070728.15341-1-david.marchand@redhat.com>

Hi David,

On 5/18/21 9:07 AM, David Marchand wrote:
> The net/vhost pmd does not comply with the ethdev offload API as it does
> not report rx/tx offload capabilities wrt TSO and checksum offloading.
> On the other hand, the net/vhost pmd lets guest negotiates TSO and
> checksum offloading.
> 
> Changing the behavior for rx/tx offload flags handling won't
> improve/fix this situation and will break applications that might have
> been relying on implicit support of TSO in this driver.
> 
> Revert this behavior change until we have a complete fix.
> 
> Fixes: ca7036b4af3a ("vhost: fix offload flags in Rx path")
> 
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
> The full fix requires:
> - reporting rx/tx_offload_capa,
> - supporting sw TSO and checksums for the case when a virtual machine
>   negotiates this feature, but the application does not configure
>   DEV_[RT]X_OFFLOAD_* appropriate flags,
> 
> ---
>  drivers/net/vhost/rte_eth_vhost.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/net/vhost/rte_eth_vhost.c b/drivers/net/vhost/rte_eth_vhost.c
> index 8524898661..a202931e9a 100644
> --- a/drivers/net/vhost/rte_eth_vhost.c
> +++ b/drivers/net/vhost/rte_eth_vhost.c
> @@ -1505,7 +1505,7 @@ rte_pmd_vhost_probe(struct rte_vdev_device *dev)
>  	int ret = 0;
>  	char *iface_name;
>  	uint16_t queues;
> -	uint64_t flags = RTE_VHOST_USER_NET_COMPLIANT_OL_FLAGS;
> +	uint64_t flags = 0;
>  	uint64_t disable_flags = 0;
>  	int client_mode = 0;
>  	int iommu_support = 0;
> 

As we discussed yesterday, I agree that's the best thing to do while
proper TSO support is implemented.

Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>

Thanks,
Maxime


  reply	other threads:[~2021-05-18  7:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-18  7:07 David Marchand
2021-05-18  7:16 ` Maxime Coquelin [this message]
2021-05-18  8:13 ` Xia, Chenbo

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=d302e730-be90-ed36-c221-67153456be57@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=chenbo.xia@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.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).