From: Eric Dumazet <eric.dumazet@gmail.com>
To: Or Gerlitz <gerlitz.or@gmail.com>,
Michael Chan <michael.chan@broadcom.com>
Cc: David Miller <davem@davemloft.net>,
Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 2/4] bnxt_en: Use NETIF_F_GRO_HW.
Date: Mon, 04 Dec 2017 14:00:45 -0800 [thread overview]
Message-ID: <1512424845.19682.64.camel@gmail.com> (raw)
In-Reply-To: <CAJ3xEMg5rS+Q=1hV8aMBQJruOH1A7-dScp_8WZwUQTJ7CKcsTg@mail.gmail.com>
On Mon, 2017-12-04 at 23:06 +0200, Or Gerlitz wrote:
> On Mon, Dec 4, 2017 at 8:11 PM, Michael Chan <michael.chan@broadcom.c
> om> wrote:
>
> > All the logic is already in these 3 drivers in the tree. You can
> > see
> > the additional logic in any of these drivers. It's just that these
> > drivers have been using NETIF_F_GRO to turn on this mode in
> > hardware/firmware.
>
> What happens for tcp encaped by some udp tunnel, does
> the HW know how to GRO that?
Yes it does, at least for common encaps (GRE, SIT, IPIP)
next prev parent reply other threads:[~2017-12-04 22:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 11:12 [PATCH net-next 0/4] Introduce NETIF_F_GRO_HW Michael Chan
2017-12-04 11:12 ` [PATCH net-next 1/4] net: " Michael Chan
2017-12-04 16:30 ` Or Gerlitz
2017-12-04 16:47 ` Alexander Duyck
2017-12-04 18:23 ` Michael Chan
2017-12-04 18:43 ` Alexander Duyck
2017-12-04 18:59 ` David Miller
2017-12-04 19:24 ` Alexander Duyck
2017-12-04 19:26 ` Eric Dumazet
2017-12-04 19:36 ` Alexander Duyck
2017-12-04 19:52 ` Michael Chan
2017-12-04 20:58 ` Alexander Duyck
2017-12-04 23:05 ` Michael Chan
2017-12-04 22:15 ` Yuval Mintz
2017-12-04 22:31 ` Michael Chan
2017-12-04 11:12 ` [PATCH net-next 2/4] bnxt_en: Use NETIF_F_GRO_HW Michael Chan
2017-12-04 16:35 ` Or Gerlitz
2017-12-04 18:11 ` Michael Chan
2017-12-04 21:06 ` Or Gerlitz
2017-12-04 22:00 ` Eric Dumazet [this message]
2017-12-05 0:07 ` Michael Chan
2017-12-05 18:10 ` Marcelo Ricardo Leitner
2017-12-06 21:04 ` Michael Chan
2017-12-04 11:12 ` [PATCH net-next 3/4] bnx2x: " Michael Chan
2017-12-04 11:12 ` [PATCH net-next 4/4] qede: " Michael Chan
2017-12-04 21:48 ` Yuval Mintz
2017-12-04 22:45 ` Michael Chan
2017-12-05 12:32 ` Chopra, Manish
2017-12-05 17:13 ` Michael Chan
2017-12-04 11:38 ` [PATCH net-next 0/4] Introduce NETIF_F_GRO_HW Elior, Ariel
2017-12-05 19:31 ` David Miller
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=1512424845.19682.64.camel@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=gerlitz.or@gmail.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
/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).