[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACKFLi=JhTRD8jK+HqDcTxJHcYzKoGXNfUXs9DKiFQULDUkKYg@mail.gmail.com>
Date: Thu, 14 Dec 2017 10:36:12 -0800
From: Michael Chan <michael.chan@...adcom.com>
To: Or Gerlitz <gerlitz.or@...il.com>
Cc: David Miller <davem@...emloft.net>,
Linux Netdev List <netdev@...r.kernel.org>,
Andy Gospodarek <andrew.gospodarek@...adcom.com>,
Gal Pressman <galp@...lanox.com>
Subject: Re: [PATCH net-next v4 0/5] Introduce NETIF_F_GRO_HW
On Thu, Dec 14, 2017 at 8:34 AM, Or Gerlitz <gerlitz.or@...il.com> wrote:
> On Mon, Dec 11, 2017 at 1:41 PM, Michael Chan <michael.chan@...adcom.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?
The motivations are the same as LRO: to achieve higher RX throughput
and lower CPU utilization.
You can think of it as an improved version of LRO that is stricter and
provides more information to construct the GRO frame so that it is
reversible.
>
> Or.
>
> [1] http://vger.kernel.org/netconf2017_files/hardware_gro.pdf
Powered by blists - more mailing lists