netdev - Re: [PATCH 00/14]: netlink: memory mapped I/O

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: <1366297052.3205.49.camel@edumazet-glaptop>
Date:	Thu, 18 Apr 2013 07:57:32 -0700
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Patrick McHardy <kaber@...sh.net>
Cc:	Florian Westphal <fw@...len.de>, davem@...emloft.net,
	netfilter-devel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH 00/14]: netlink: memory mapped I/O

On Thu, 2013-04-18 at 12:27 +0200, Patrick McHardy wrote:

> No need to be sorry :) The use cases only partially overlap, the zero copy
> (actually single copy, just like mmaped netlink) requires drivers to generate
> fragmented skbs, while the mmaped netlink code works in all cases.

In fact all NIC drivers provides suitable skb in their RX path, as
skb->head is now a fragment too. 

So the 'zero copy' code should work for all drivers.

It might be possible to do the same in transmit path, if needed.


--
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