netdev - Re: [PATCH net-next] tsnep: Inline small fragments within TX descriptor

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] [day] [month] [year] [list]

Message-Id: 
 <169744682505.7474.1136319975584731643.git-patchwork-notify@kernel.org>
Date: Mon, 16 Oct 2023 09:00:25 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Gerhard Engleder <gerhard@...leder-embedded.com>
Cc: netdev@...r.kernel.org, davem@...emloft.net, kuba@...nel.org,
 edumazet@...gle.com, pabeni@...hat.com
Subject: Re: [PATCH net-next] tsnep: Inline small fragments within TX descriptor

Hello:

This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@...emloft.net>:

On Wed, 11 Oct 2023 20:21:54 +0200 you wrote:
> The tsnep network controller is able to extend the descriptor directly
> with data to be transmitted. In this case no TX data DMA address is
> necessary. Instead of the TX data DMA address the TX data buffer is
> placed at the end of the descriptor.
> 
> The descriptor is read with a 64 bytes DMA read by the tsnep network
> controller. If the sum of descriptor data and TX data is less than or
> equal to 64 bytes, then no additional DMA read is necessary to read the
> TX data. Therefore, it makes sense to inline small fragments up to this
> limit within the descriptor ring.
> 
> [...]

Here is the summary with links:
  - [net-next] tsnep: Inline small fragments within TX descriptor
    https://git.kernel.org/netdev/net-next/c/dccce1d7c040

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html