From: Wei Liu <wei.liu2@citrix.com>
To: <xen-devel@lists.xen.org>, <netdev@vger.kernel.org>
Cc: <ian.campbell@citrix.com>, <david.vrabel@citrix.com>,
<zoltan.kiss@citrix.com>, <paul.durrant@citrix.com>,
<a.j.bennieston@gmail.com>, <wei.liu2@citrix.com>
Subject: [PATCH net-next v10 0/7]
Date: Wed, 4 Jun 2014 10:30:40 +0100 [thread overview]
Message-ID: <1401874247-3202-1-git-send-email-wei.liu2@citrix.com> (raw)
This is rebased version of Andrew's V8 patch series. The original cover letter
can be found at
http://lwn.net/Articles/598559/
or with message ID:
<1400075550-4580-1-git-send-email-andrew.bennieston@citrix.com>
I rebased this on top of net-next. No functional change is introduced. The
patch that needed some extra care was "xen-netback: Factor queue-specific data
into queue struct" because it clashed with a fix introduced in net. A simple
test of creating guest, iperf, then shutting down guest worked as expected.
The last patch fixes a minor problem that queue name is not initialised in
xen-netfront, resulting in names like "-tx" "-rx" in /proc/interrupt.
Changes since v9 (no functional change introduced):
* include commit summary in the commit message of first patch
* fold David Vrabel's Reviewed-by into last patch
Wei.
Andrew J. Bennieston (5):
xen-netback: Move grant_copy_op array back into struct xenvif.
xen-netback: Add support for multiple queues
xen-netfront: Factor queue-specific data into queue struct.
xen-netfront: Add support for multiple queues
xen-net{back,front}: Document multi-queue feature in netif.h
Wei Liu (2):
xen-netback: Factor queue-specific data into queue struct
xen-netfront: initialise queue name in xennet_init_queue
drivers/net/xen-netback/common.h | 107 ++--
drivers/net/xen-netback/interface.c | 522 ++++++++++------
drivers/net/xen-netback/netback.c | 718 +++++++++++-----------
drivers/net/xen-netback/xenbus.c | 182 +++++-
drivers/net/xen-netfront.c | 1121 ++++++++++++++++++++++-------------
include/xen/interface/io/netif.h | 53 ++
6 files changed, 1680 insertions(+), 1023 deletions(-)
--
1.7.10.4
next reply other threads:[~2014-06-04 9:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 9:30 Wei Liu [this message]
2014-06-04 9:30 ` [PATCH net-next v10 1/7] xen-netback: Move grant_copy_op array back into struct xenvif Wei Liu
2014-06-04 14:46 ` Sergei Shtylyov
2014-06-04 14:52 ` David Vrabel
2014-06-04 15:00 ` Sergei Shtylyov
2014-06-04 15:03 ` Wei Liu
2014-06-04 9:30 ` [PATCH net-next v10 2/7] xen-netback: Factor queue-specific data into queue struct Wei Liu
2014-06-04 9:30 ` [PATCH net-next v10 3/7] xen-netback: Add support for multiple queues Wei Liu
2014-06-04 9:30 ` [PATCH net-next v10 4/7] xen-netfront: Factor queue-specific data into queue struct Wei Liu
2014-06-04 9:30 ` [PATCH net-next v10 5/7] xen-netfront: Add support for multiple queues Wei Liu
2014-06-04 9:30 ` [PATCH net-next v10 6/7] xen-net{back,front}: Document multi-queue feature in netif.h Wei Liu
2014-06-04 9:30 ` [PATCH net-next v10 7/7] xen-netfront: initialise queue name in xennet_init_queue Wei Liu
2014-06-04 9:35 ` Andrew J. Bennieston
2014-06-04 21:49 ` [PATCH net-next v10 0/7] David Miller
2014-06-04 22:27 ` 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=1401874247-3202-1-git-send-email-wei.liu2@citrix.com \
--to=wei.liu2@citrix.com \
--cc=a.j.bennieston@gmail.com \
--cc=david.vrabel@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=netdev@vger.kernel.org \
--cc=paul.durrant@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=zoltan.kiss@citrix.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).