netdev - Re: [PATCH 0/3] mvneta: software TSO implementation

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]

Message-Id: <20140411.022006.1718259701974368498.davem@davemloft.net>
Date:	Fri, 11 Apr 2014 02:20:06 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	w@....eu
Cc:	eric.dumazet@...il.com, ezequiel.garcia@...e-electrons.com,
	netdev@...r.kernel.org, thomas.petazzoni@...e-electrons.com,
	gregory.clement@...e-electrons.com, simon.guinot@...uanux.org,
	tawfik@...vell.com, alior@...vell.com
Subject: Re: [PATCH 0/3] mvneta: software TSO implementation

From: Willy Tarreau <w@....eu>
Date: Fri, 11 Apr 2014 07:48:47 +0200

> I also tried to find how to do this for mv643xx_eth a few years ago
> based on other drivers (eg: tilegx) and failed to find anything
> common. At this level, we're really playing with the NIC's descriptors,
> and many of them have different capabilities (eg: HW checksums for all
> frames, VLAN or none, etc...). I don't really see how this could be
> factorized, and since many NICs do support TSO, I'm not convinced by
> the effort.

I wanted to hook this into the NIU driver as well, which also lacks
TSO support.

The descriptor and checksum part is chip specific, but the segmentation
of the buffer segments, calculating the number of necessary descriptors,
etc. absolutely is not.

Please work on finding a suitable abstraction, it's possible.
--
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