From: Or Gerlitz <gerlitz.or@gmail.com>
To: Michael Chan <michael.chan@broadcom.com>
Cc: David Miller <davem@davemloft.net>,
Linux Netdev List <netdev@vger.kernel.org>,
Andy Gospodarek <andrew.gospodarek@broadcom.com>,
Gal Pressman <galp@mellanox.com>
Subject: Re: [PATCH net-next v4 0/5] Introduce NETIF_F_GRO_HW
Date: Thu, 14 Dec 2017 18:34:28 +0200 [thread overview]
Message-ID: <CAJ3xEMhMOj_y7d-4aE3OxL+D3zhYSVpBA+iJihFP8DiH5R8t2g@mail.gmail.com> (raw)
In-Reply-To: <1512992470-28861-1-git-send-email-michael.chan@broadcom.com>
On Mon, Dec 11, 2017 at 1:41 PM, Michael Chan <michael.chan@broadcom.com> wrote:
> Introduce NETIF_F_GRO_HW feature flag and convert drivers that support
> hardware GRO to use the new flag.
Hi Michael,
Could you add more performance motivations/results? looking on your
netconf slides [1]
I see (much) better CPU utilization (slide 5) -- do you have more
numbers to share?
Or.
[1] http://vger.kernel.org/netconf2017_files/hardware_gro.pdf
next prev parent reply other threads:[~2017-12-14 16:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 11:41 [PATCH net-next v4 0/5] Introduce NETIF_F_GRO_HW Michael Chan
2017-12-11 11:41 ` [PATCH net-next v4 1/5] net: " Michael Chan
2017-12-12 15:57 ` Alexander Duyck
2017-12-11 11:41 ` [PATCH net-next v4 2/5] net: Disable GRO_HW when generic XDP is installed on a device Michael Chan
2017-12-11 11:41 ` [PATCH net-next v4 3/5] bnxt_en: Use NETIF_F_GRO_HW Michael Chan
2017-12-11 11:41 ` [PATCH net-next v4 4/5] bnx2x: " Michael Chan
2017-12-13 9:08 ` Chopra, Manish
2017-12-13 20:45 ` Michael Chan
2017-12-14 7:46 ` Chopra, Manish
2017-12-14 7:59 ` Michael Chan
2017-12-15 7:07 ` Chopra, Manish
2017-12-15 7:56 ` Michael Chan
2017-12-11 11:41 ` [PATCH net-next v4 5/5] qede: " Michael Chan
2017-12-14 16:34 ` Or Gerlitz [this message]
2017-12-14 18:36 ` [PATCH net-next v4 0/5] Introduce NETIF_F_GRO_HW Michael Chan
2017-12-14 20:01 ` Or Gerlitz
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=CAJ3xEMhMOj_y7d-4aE3OxL+D3zhYSVpBA+iJihFP8DiH5R8t2g@mail.gmail.com \
--to=gerlitz.or@gmail.com \
--cc=andrew.gospodarek@broadcom.com \
--cc=davem@davemloft.net \
--cc=galp@mellanox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.