From: Ganesh Goudar <ganeshgr@chelsio.com>
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: Netdev <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
nirranjan@chelsio.com, indranil@chelsio.com,
venkatesh@chelsio.com, Arjun Vynipadath <arjun@chelsio.com>
Subject: Re: [PATCH net-next] cxgb4vf: Fix netdev_features flag
Date: Fri, 1 Dec 2017 21:28:21 +0530 [thread overview]
Message-ID: <20171201155817.GA18552@chelsio.com> (raw)
In-Reply-To: <CAKgT0UcG7PoYrqnhvpBycySoRJVCShDo+MiheMy9CUh4sR-hBQ@mail.gmail.com>
On Friday, December 12/01/17, 2017 at 07:16:38 -0800, Alexander Duyck wrote:
> On Fri, Dec 1, 2017 at 6:59 AM, Ganesh Goudar <ganeshgr@chelsio.com> wrote:
> > GRO is not supported by Chelsio HW when rx_csum is disabled.
> > Update the netdev features flag when rx_csum is modified.
> >
> > Signed-off-by: Arjun Vynipadath <arjun@chelsio.com>
> > Signed-off-by: Ganesh Goudar <ganeshgr@chelsio.com>
> > ---
> > drivers/net/ethernet/chelsio/cxgb4vf/cxgb4vf_main.c | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/drivers/net/ethernet/chelsio/cxgb4vf/cxgb4vf_main.c b/drivers/net/ethernet/chelsio/cxgb4vf/cxgb4vf_main.c
> > index b48361c..8e993ac 100644
> > --- a/drivers/net/ethernet/chelsio/cxgb4vf/cxgb4vf_main.c
> > +++ b/drivers/net/ethernet/chelsio/cxgb4vf/cxgb4vf_main.c
> > @@ -1114,6 +1114,10 @@ static int cxgb4vf_change_mtu(struct net_device *dev, int new_mtu)
> > static netdev_features_t cxgb4vf_fix_features(struct net_device *dev,
> > netdev_features_t features)
> > {
> > + /* Disable GRO, if RX_CSUM is disabled */
> > + if (!(features & NETIF_F_RXCSUM))
> > + features &= ~NETIF_F_GRO;
> > +
> > /*
> > * Since there is no support for separate rx/tx vlan accel
> > * enable/disable make sure tx flag is always in same state as rx.
>
> Wouldn't it make more sense to just put this in netdev_fix_features? I
> would thing GRO cannot be supported on any device if RX_CSUM is
> disabled since GRO depends on checksum validation from the hardware
> before it can aggregate the frame.
>
> - Alex
Makes sense, but let us see what others has to say.
Ganesh
next prev parent reply other threads:[~2017-12-01 15:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 14:59 [PATCH net-next] cxgb4vf: Fix netdev_features flag Ganesh Goudar
2017-12-01 15:16 ` Alexander Duyck
2017-12-01 15:58 ` Ganesh Goudar [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-10-23 10:03 Ganesh Goudar
2017-10-23 12:13 ` David Miller
2017-10-23 13:08 ` kbuild test robot
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=20171201155817.GA18552@chelsio.com \
--to=ganeshgr@chelsio.com \
--cc=alexander.duyck@gmail.com \
--cc=arjun@chelsio.com \
--cc=davem@davemloft.net \
--cc=indranil@chelsio.com \
--cc=netdev@vger.kernel.org \
--cc=nirranjan@chelsio.com \
--cc=venkatesh@chelsio.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).