netdev - Re: [Xen-devel] [PATCH V8 net-next 0/6] xen-net{back, front}: Multiple transmit and receive queues

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

Date:	Wed, 14 May 2014 16:09:23 +0200
From:	Sander Eikelenboom <linux@...elenboom.it>
To:	"Andrew J. Bennieston" <andrew.bennieston@...rix.com>
CC:	xen-devel@...ts.xenproject.org, davem@...emloft.net,
	wei.liu2@...rix.com, <ian.campbell@...rix.com>,
	<netdev@...r.kernel.org>, <paul.durrant@...rix.com>,
	<david.vrabel@...rix.com>, <zoltan.kiss@...rix.com>
Subject: Re: [Xen-devel] [PATCH V8 net-next 0/6] xen-net{back, front}: Multiple transmit and receive queues


Wednesday, May 14, 2014, 3:52:24 PM, you wrote:

> This patch series implements multiple transmit and receive queues (i.e.
> multiple shared rings) for the xen virtual network interfaces.

> The series is split up as follows:
>  - Patch 1 brings the 'grant_copy_op' array back into struct xenvif, in
>    preparation for multi-queue support. See the patch itself for more details.
> - Patches 2 and 4 factor out the queue-specific data for netback and
>   netfront respectively, and modify the rest of the code to use these
>   as appropriate.
> - Patches 3 and 5 introduce new XenStore keys to negotiate and use
>   multiple shared rings and event channels, and code to connect these
>   as appropriate.
> - Patch 6 documents the XenStore keys required for the new feature
>   in include/xen/interface/io/netif.h

> All other transmit and receive processing remains unchanged, i.e. there
> is a kthread per queue and a NAPI context per queue.

> The performance of these patches has been analysed in detail, with
> results available at:

<snip>

Would it be possible to also put these somewhere in a tree (or branch of the 
xen-tree), so it is more easy to pull and test ?

--
Sander

> --
> Andrew J. Bennieston



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