From: Wei Liu <wei.liu2@citrix.com>
To: Paul Durrant <paul.durrant@citrix.com>
Cc: <xen-devel@lists.xenproject.org>, <netdev@vger.kernel.org>,
Wei Liu <wei.liu2@citrix.com>
Subject: Re: [PATCH net-next v3 2/4] xen-netback: add control protocol implementation
Date: Wed, 11 May 2016 17:02:45 +0100 [thread overview]
Message-ID: <20160511160245.GH8063@citrix.com> (raw)
In-Reply-To: <1462980817-10149-3-git-send-email-paul.durrant@citrix.com>
On Wed, May 11, 2016 at 04:33:35PM +0100, Paul Durrant wrote:
> My recent patch to include/xen/interface/io/netif.h defines a new shared
> ring (in addition to the rx and tx rings) for passing control messages
> from a VM frontend driver to a backend driver.
>
> A previous patch added the necessary boilerplate for mapping the control
> ring from the frontend, should it be created. This patch adds
> implementations for each of the defined protocol messages.
>
> Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
Acked-by: Wei Liu <wei.liu2@citrix.com>
next prev parent reply other threads:[~2016-05-11 16:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 15:33 [PATCH net-next v3 0/4] xen-netback: support for control ring Paul Durrant
2016-05-11 15:33 ` [PATCH net-next v3 1/4] xen-netback: add control ring boilerplate Paul Durrant
2016-05-11 15:33 ` Paul Durrant
2016-05-11 16:02 ` Wei Liu
2016-05-11 16:02 ` Wei Liu
2016-05-11 15:33 ` [PATCH net-next v3 2/4] xen-netback: add control protocol implementation Paul Durrant
2016-05-11 16:02 ` Wei Liu
2016-05-11 16:02 ` Wei Liu [this message]
2016-05-11 15:33 ` Paul Durrant
2016-05-11 15:33 ` [PATCH net-next v3 3/4] xen-netback: pass hash value to the frontend Paul Durrant
2016-05-11 15:33 ` Paul Durrant
2016-05-11 15:33 ` [PATCH net-next v3 4/4] xen-netback: use hash value from " Paul Durrant
2016-05-11 15:33 ` Paul Durrant
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=20160511160245.GH8063@citrix.com \
--to=wei.liu2@citrix.com \
--cc=netdev@vger.kernel.org \
--cc=paul.durrant@citrix.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.