netdev - Re: [PATCH net-next] net: introduce netdevice gso_min

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Mon, 06 Oct 2014 17:21:49 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	eric.dumazet@...il.com
Cc:	amirv@...lanox.com, edumazet@...gle.com, netdev@...r.kernel.org,
	yevgenyp@...lanox.com, ogerlitz@...lanox.com, idos@...lanox.com
Subject: Re: [PATCH net-next] net: introduce netdevice gso_min_segs
 attribute

From: Eric Dumazet <eric.dumazet@...il.com>
Date: Sun, 05 Oct 2014 10:11:27 -0700

> From: Eric Dumazet <edumazet@...gle.com>
> 
> Some TSO engines might have a too heavy setup cost, that impacts
> performance on hosts sending small bursts (2 MSS per packet).
> 
> This patch adds a device gso_min_segs, allowing drivers to set
> a minimum segment size for TSO packets, according to the NIC
> performance.
> 
> Tested on a mlx4 NIC, this allows to get a ~110% increase of
> throughput when sending 2 MSS per packet.
> 
> Signed-off-by: Eric Dumazet <edumazet@...gle.com>

So exactly what value are you using for mlx4?

Because I wonder if we should just generically forfeit TSO unless
we have > 2 segments, for example.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html