From: Wei Liu <wei.liu2@citrix.com>
To: <xen-devel@lists.xen.org>, <netdev@vger.kernel.org>
Cc: <ian.campbell@citrix.com>, <konrad.wilk@oracle.com>,
<david.vrabel@citrix.com>, Wei Liu <wei.liu2@citrix.com>
Subject: [PATCH net-next 0/2 V2] Xen network: split event channels support
Date: Tue, 21 May 2013 19:35:08 +0100 [thread overview]
Message-ID: <1369161310-9529-1-git-send-email-wei.liu2@citrix.com> (raw)
This series adds a new feature called split event channels.
In the original implementation, only one event channel is setup between
frontend and backend. This is not ideal as TX notification interferes with RX
notification. Using dedicated event channels for TX and RX solves this issue.
Changes since V1:
* change subject lines of commits to be more specific
* add parameter feature_split_event_channels for xen-netback
* remove two dev_info
Wei Liu (2):
xen-netback: split event channels support for Xen backend driver
xen-netfront: split event channels support for Xen frontend driver
drivers/net/xen-netback/common.h | 13 ++-
drivers/net/xen-netback/interface.c | 84 ++++++++++++++---
drivers/net/xen-netback/netback.c | 14 ++-
drivers/net/xen-netback/xenbus.c | 40 ++++++--
drivers/net/xen-netfront.c | 173 +++++++++++++++++++++++++++++------
5 files changed, 266 insertions(+), 58 deletions(-)
--
1.7.10.4
next reply other threads:[~2013-05-21 18:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 18:35 Wei Liu [this message]
2013-05-21 18:35 ` [PATCH net-next V2 1/2] xen-netback: split event channels support for Xen backend driver Wei Liu
2013-05-22 8:05 ` [Xen-devel] " Jan Beulich
2013-05-22 15:17 ` Konrad Rzeszutek Wilk
2013-05-22 15:35 ` Wei Liu
2013-05-22 15:40 ` annie li
2013-05-22 15:50 ` Wei Liu
2013-05-21 18:35 ` [PATCH net-next V2 2/2] xen-netfront: split event channels support for Xen frontend driver Wei Liu
2013-05-22 8:13 ` [Xen-devel] " Jan Beulich
2013-05-22 8:35 ` [PATCH net-next 0/2 V2] Xen network: split event channels support Ian Campbell
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=1369161310-9529-1-git-send-email-wei.liu2@citrix.com \
--to=wei.liu2@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=xen-devel@lists.xen.org \
/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).