From: David Miller <davem@davemloft.net>
To: michael.chan@broadcom.com
Cc: alexander.duyck@gmail.com, sd@queasysnail.net,
netdev@vger.kernel.org, andrew.gospodarek@broadcom.com
Subject: Re: [PATCH net-next v5 0/5] Introduce NETIF_F_GRO_HW
Date: Sat, 30 Dec 2017 10:45:35 -0500 (EST) [thread overview]
Message-ID: <20171230.104535.2291382569309825655.davem@davemloft.net> (raw)
In-Reply-To: <CACKFLikJjJHV__GfyFFCyTi_UYKP0JEOa69UmZQuvjd91fjM2Q@mail.gmail.com>
From: Michael Chan <michael.chan@broadcom.com>
Date: Fri, 29 Dec 2017 21:20:02 -0800
> I think the name GRO_HW is perfectly fine. It is GRO aggregation done
> in hardware, and hardware providing extra information to the driver to
> setup the SKB just like GRO. I don't know what better name to call it
> than GRO_HW.
Agreed.
next prev parent reply other threads:[~2017-12-30 15:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-16 8:09 [PATCH net-next v5 0/5] Introduce NETIF_F_GRO_HW Michael Chan
2017-12-16 8:09 ` [PATCH net-next v5 1/5] net: " Michael Chan
2017-12-16 16:38 ` Alexander Duyck
2017-12-16 8:09 ` [PATCH net-next v5 2/5] net: Disable GRO_HW when generic XDP is installed on a device Michael Chan
2017-12-16 8:09 ` [PATCH net-next v5 3/5] bnxt_en: Use NETIF_F_GRO_HW Michael Chan
2017-12-16 8:09 ` [PATCH net-next v5 4/5] bnx2x: " Michael Chan
2017-12-17 11:49 ` Chopra, Manish
2017-12-16 8:09 ` [PATCH net-next v5 5/5] qede: " Michael Chan
2017-12-17 11:52 ` Chopra, Manish
2017-12-19 15:50 ` [PATCH net-next v5 0/5] Introduce NETIF_F_GRO_HW David Miller
2017-12-19 19:04 ` Marcelo Ricardo Leitner
2017-12-19 19:24 ` David Miller
2017-12-19 19:25 ` Michael Chan
2017-12-19 19:55 ` Marcelo Ricardo Leitner
2017-12-22 14:57 ` Sabrina Dubroca
2017-12-22 18:14 ` Alexander Duyck
2017-12-29 12:43 ` Sabrina Dubroca
2017-12-29 15:12 ` Alexander Duyck
2017-12-30 5:20 ` Michael Chan
2017-12-30 15:45 ` David Miller [this message]
2019-01-07 14:00 ` Shay Agroskin
2019-01-07 14:46 ` David Miller
2019-01-08 10:58 ` Michael Chan
2019-01-13 10:36 ` Shay Agroskin
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=20171230.104535.2291382569309825655.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexander.duyck@gmail.com \
--cc=andrew.gospodarek@broadcom.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.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).