From: Andrew Bennieston <andrew.bennieston@citrix•com>
To: Wei Liu <wei.liu2@citrix•com>, Sander Eikelenboom <linux@eikelenboom•it>
Cc: <xen-devel@lists•xenproject.org>, <davem@davemloft•net>,
<ian.campbell@citrix•com>, <netdev@vger•kernel.org>,
<paul.durrant@citrix•com>, <david.vrabel@citrix•com>,
<zoltan.kiss@citrix•com>
Subject: Re: [Xen-devel] [PATCH V8 net-next 0/6] xen-net{back, front}: Multiple transmit and receive queues
Date: Wed, 14 May 2014 17:18:31 +0100 [thread overview]
Message-ID: <53739757.5060905@citrix.com> (raw)
In-Reply-To: <20140514141347.GR6332@zion.uk.xensource.com>
On 14/05/14 15:13, Wei Liu wrote:
> On Wed, May 14, 2014 at 04:09:23PM +0200, Sander Eikelenboom wrote:
>>
>> 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 ?
>>
>
> I cannot speak for Andrew. FWIW you can save this thread and use 'git
> am' to apply them to 'net-next'.
>
> Wei.
I don't currently have a public-facing git repo for this. If you'd
prefer I can send you the patches directly in a tarball, which you may
be able to apply more easily than grabbing them from email threads?
- Andrew
>
>> --
>> Sander
>>
>>> --
>>> Andrew J. Bennieston
>>
>>
next prev parent reply other threads:[~2014-05-14 16:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 13:52 [PATCH V8 net-next 0/6] xen-net{back, front}: Multiple transmit and receive queues Andrew J. Bennieston
2014-05-14 13:52 ` [PATCH V8 net-next 1/6] xen-netback: Move grant_copy_op array back into struct xenvif Andrew J. Bennieston
2014-05-14 13:52 ` [PATCH V8 net-next 2/6] xen-netback: Factor queue-specific data into queue struct Andrew J. Bennieston
2014-05-14 13:58 ` Wei Liu
2014-05-14 13:52 ` [PATCH V8 net-next 3/6] xen-netback: Add support for multiple queues Andrew J. Bennieston
2014-05-14 13:59 ` Wei Liu
2014-05-14 13:52 ` [PATCH V8 net-next 4/6] xen-netfront: Factor queue-specific data into queue struct Andrew J. Bennieston
2014-05-14 13:52 ` [PATCH V8 net-next 5/6] xen-netfront: Add support for multiple queues Andrew J. Bennieston
2014-05-14 13:52 ` [PATCH V8 net-next 6/6] xen-net{back, front}: Document multi-queue feature in netif.h Andrew J. Bennieston
2014-05-14 14:09 ` [Xen-devel] [PATCH V8 net-next 0/6] xen-net{back, front}: Multiple transmit and receive queues Sander Eikelenboom
2014-05-14 14:13 ` Wei Liu
2014-05-14 16:18 ` Andrew Bennieston [this message]
2014-05-14 18:37 ` Sander Eikelenboom
2014-05-14 21:24 ` Wei Liu
2014-05-14 21:36 ` Sander Eikelenboom
2014-05-21 14:42 ` Paul Durrant
2014-05-27 23:10 ` [Xen-devel] " Wei Liu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53739757.5060905@citrix.com \
--to=andrew.bennieston@citrix$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=david.vrabel@citrix$(echo .)com \
--cc=ian.campbell@citrix$(echo .)com \
--cc=linux@eikelenboom$(echo .)it \
--cc=netdev@vger$(echo .)kernel.org \
--cc=paul.durrant@citrix$(echo .)com \
--cc=wei.liu2@citrix$(echo .)com \
--cc=xen-devel@lists$(echo .)xenproject.org \
--cc=zoltan.kiss@citrix$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox