From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Miller <davem@davemloft.net>
Subject: Re: [PATCH net-next v5 0/5] Introduce NETIF_F_GRO_HW
Date: Mon, 07 Jan 2019 06:46:52 -0800 (PST)
Message-ID: <20190107.064652.837217035297962007.davem@davemloft.net>
References: <1513411784-17653-1-git-send-email-michael.chan@broadcom.com>
        <AM6PR05MB519143027C680A3CDA578C1CA0890@AM6PR05MB5191.eurprd05.prod.outlook.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: michael.chan@broadcom.com, netdev@vger.kernel.org,
        andrew.gospodarek@broadcom.com, tariqt@mellanox.com,
        eranbe@mellanox.com, saeedm@mellanox.com
To: shayag@mellanox.com
Return-path: <netdev-owner@vger.kernel.org>
Received: from shards.monkeyblade.net ([23.128.96.9]:56286 "EHLO
        shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1727242AbfAGOq5 (ORCPT
        <rfc822;netdev@vger.kernel.org>); Mon, 7 Jan 2019 09:46:57 -0500
In-Reply-To: <AM6PR05MB519143027C680A3CDA578C1CA0890@AM6PR05MB5191.eurprd05.prod.outlook.com>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

From: Shay Agroskin <shayag@mellanox.com>
Date: Mon, 7 Jan 2019 14:00:33 +0000

> 2) While we understand that implementing GRO in HW can result in
> performance gain, is HW-GRO's singularity in its ability to
> construct packets that can be re-segmented? (as appose to LRO).
> What else is expected from HW when turning it on?

This is the basic requirement, that the original packet stream can
be accurately reconstituted from the HW GRO packet.