netdev - Re: [PATCH net-next v5 0/5] Introduce NETIF_F_GRO

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20190107.064652.837217035297962007.davem@davemloft.net>
Date:   Mon, 07 Jan 2019 06:46:52 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     shayag@...lanox.com
Cc:     michael.chan@...adcom.com, netdev@...r.kernel.org,
        andrew.gospodarek@...adcom.com, tariqt@...lanox.com,
        eranbe@...lanox.com, saeedm@...lanox.com
Subject: Re: [PATCH net-next v5 0/5] Introduce NETIF_F_GRO_HW

From: Shay Agroskin <shayag@...lanox.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.