Re: [PATCH 2/2] hv_netvsc: Use VF's tso_max_size value when data path is VF | netdev | Ratatoskr

[PATCH 0/2] Enable Big TCP for MANA devices · Shradha Gupta <hidden> · 2025-02-05
[PATCH 1/2] net: mana: Allow tso_max_size to go up-to GSO_MAX_SIZE in MANA · Shradha Gupta <hidden> · 2025-02-05
[PATCH 2/2] hv_netvsc: Use VF's tso_max_size value when data path is VF · Shradha Gupta <hidden> · 2025-02-05
Re: [PATCH 2/2] hv_netvsc: Use VF's tso_max_size value when data path is VF · Stephen Hemminger <stephen@networkplumber.org> · 2025-02-05
Re: [PATCH 2/2] hv_netvsc: Use VF's tso_max_size value when data path is VF · Shradha Gupta <hidden> · 2025-02-05
Re: [PATCH 2/2] hv_netvsc: Use VF's tso_max_size value when data path is VF · Jakub Kicinski <kuba@kernel.org> · 2025-02-06
Re: [PATCH 2/2] hv_netvsc: Use VF's tso_max_size value when data path is VF · Shradha Gupta <hidden> · 2025-02-06

Re: [PATCH 2/2] hv_netvsc: Use VF's tso_max_size value when data path is VF

From: Shradha Gupta <hidden>
Date: 2025-02-06 04:48:33
Also in: linux-hyperv, lkml

On Wed, Feb 05, 2025 at 06:43:19PM -0800, Jakub Kicinski wrote:

On Tue,  4 Feb 2025 20:21:55 -0800 Shradha Gupta wrote:

quoted

Therefore, we use netif_set_tso_max_size() to set max segment size

I think the term "segment" is used incorrectly throughout the patch ?
Isn't the right term "superframe", "aggregate" or some such ?

Thanks Jakub, I think you are right. 'aggregate' or 'aggregated pkt'
would be a more accurate term. I'll have this incorporated in the next
version.

-- 
pw-bot: cr