From: Wei Liu <wei.liu2@citrix.com>
To: Paul Durrant <paul.durrant@citrix.com>
Cc: <netdev@vger.kernel.org>, <xen-devel@lists.xenproject.org>,
Wei Liu <wei.liu2@citrix.com>
Subject: Re: [PATCH net-next 2/3] xen-netback: support multiple extra info fragments passed from frontend
Date: Thu, 10 Mar 2016 17:23:43 +0000 [thread overview]
Message-ID: <20160310172343.GR31271@citrix.com> (raw)
In-Reply-To: <1457613028-10381-3-git-send-email-paul.durrant@citrix.com>
On Thu, Mar 10, 2016 at 12:30:27PM +0000, Paul Durrant wrote:
> The code does not currently support a frontend passing multiple extra info
> fragments to the backend in a tx request. The xenvif_get_extras() function
> handles multiple extra_info fragments but make_tx_response() assumes there
> is only ever a single extra info fragment.
>
> This patch modifies xenvif_get_extras() to pass back a count of extra
> info fragments, which is then passed to make_tx_response() (after
> possibly being stashed in pending_tx_info for deferred responses).
>
> Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
> Cc: Wei Liu <wei.liu2@citrix.com>
Acked-by: Wei Liu <wei.liu2@citrix.com>
next prev parent reply other threads:[~2016-03-10 17:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 12:30 [PATCH net-next 0/3] xen-netback: fix multiple extra info handling Paul Durrant
2016-03-10 12:30 ` [PATCH net-next 1/3] xen-netback: re-import canonical netif header Paul Durrant
2016-03-10 12:30 ` Paul Durrant
2016-03-10 17:23 ` Wei Liu
2016-03-10 17:23 ` Wei Liu
2016-03-10 12:30 ` [PATCH net-next 2/3] xen-netback: support multiple extra info fragments passed from frontend Paul Durrant
2016-03-10 17:23 ` Wei Liu
2016-03-10 17:23 ` Wei Liu [this message]
2016-03-10 12:30 ` Paul Durrant
2016-03-10 12:30 ` [PATCH net-next 3/3] xen-netback: reduce log spam Paul Durrant
2016-03-10 12:30 ` Paul Durrant
2016-03-10 17:23 ` Wei Liu
2016-03-10 17:23 ` Wei Liu
2016-03-14 2:08 ` [PATCH net-next 0/3] xen-netback: fix multiple extra info handling David Miller
2016-03-14 2:08 ` David Miller
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=20160310172343.GR31271@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.