From: David Miller <davem@davemloft.net>
To: doshir@vmware.com
Cc: netdev@vger.kernel.org, pv-drivers@vmware.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] vmxnet3: turn off lro when rxcsum is disabled
Date: Tue, 04 Jun 2019 20:06:07 -0700 (PDT) [thread overview]
Message-ID: <20190604.200607.239727257233292079.davem@davemloft.net> (raw)
In-Reply-To: <20190604065838.22243-1-doshir@vmware.com>
From: Ronak Doshi <doshir@vmware.com>
Date: Mon, 3 Jun 2019 23:58:38 -0700
> Currently, when rx csum is disabled, vmxnet3 driver does not turn
> off lro, which can cause performance issues if user does not turn off
> lro explicitly. This patch adds fix_features support which is used to
> turn off LRO whenever RXCSUM is disabled.
>
> Signed-off-by: Ronak Doshi <doshir@vmware.com>
> Acked-by: Rishi Mehta <rmehta@vmware.com>
Applied.
prev parent reply other threads:[~2019-06-05 3:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 6:58 [PATCH net-next] vmxnet3: turn off lro when rxcsum is disabled Ronak Doshi
2019-06-05 3:06 ` David Miller [this message]
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=20190604.200607.239727257233292079.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=doshir@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pv-drivers@vmware.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).