From: Andrew Bennieston <andrew.bennieston@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: <xen-devel@lists.xenproject.org>, <davem@davemloft.net>,
<ian.campbell@citrix.com>, <paul.durrant@citrix.com>,
<netdev@vger.kernel.org>, <david.vrabel@citrix.com>,
<zoltan.kiss@citrix.com>
Subject: Re: [PATCH V7 net-next 4/7] xen-netback: Correctly clean up after queue initialisation error.
Date: Wed, 30 Apr 2014 17:46:05 +0100 [thread overview]
Message-ID: <536128CD.3010705@citrix.com> (raw)
In-Reply-To: <20140430144954.GA19082@zion.uk.xensource.com>
On 30/04/14 15:49, Wei Liu wrote:
> On Tue, Apr 29, 2014 at 02:27:12PM +0100, Andrew J. Bennieston wrote:
>> From: "Andrew J. Bennieston" <andrew.bennieston@citrix.com>
>>
>> Multiple queues were introduced in the previous patch, but if the
>> initialisation of a queue failed, earlier queues would not be cleaned
>> up. This patch adds cleanup logic for this scenario, making use of code
>> from the regular teardown sequence.
>>
>
> Shouldn't this patch be folded into that "previous patch" which
> introduced this problem? I see you did this for netfront patch already.
>
> Wei.
>
The netfront patch included this from the beginning; I simply forgot to
implement it in netback. I added it as a separate patch to make it
easier to review, but I can certainly merge it in with the other one
(and indeed should do so to maintain correct behaviour e.g. during a
bisect).
I think I'd rather receive comments on this separately, then if
necessary either repost the series with this folded into the relevant
patch for final merge, or post V8 with it folded after comments have
been addressed. Especially since this patch series already has some very
long patches...
Andrew.
next prev parent reply other threads:[~2014-04-30 16:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 13:27 [PATCH V7 net-next] xen-net{back, front}: Multiple transmit and receive queues Andrew J. Bennieston
2014-04-29 13:27 ` [PATCH V7 net-next 1/7] xen-netback: Move grant_copy_op array back into struct xenvif Andrew J. Bennieston
2014-04-30 14:50 ` Wei Liu
2014-04-29 13:27 ` [PATCH V7 net-next 2/7] xen-netback: Factor queue-specific data into queue struct Andrew J. Bennieston
2014-04-29 13:27 ` [PATCH V7 net-next 3/7] xen-netback: Add support for multiple queues Andrew J. Bennieston
2014-04-29 13:27 ` [PATCH V7 net-next 4/7] xen-netback: Correctly clean up after queue initialisation error Andrew J. Bennieston
2014-04-30 14:49 ` Wei Liu
2014-04-30 16:46 ` Andrew Bennieston [this message]
2014-04-29 13:27 ` [PATCH V7 net-next 5/7] xen-netfront: Factor queue-specific data into queue struct Andrew J. Bennieston
2014-04-30 14:51 ` Wei Liu
2014-04-30 14:59 ` [Xen-devel] " David Vrabel
2014-04-29 13:27 ` [PATCH V7 net-next 6/7] xen-netfront: Add support for multiple queues Andrew J. Bennieston
2014-04-30 14:51 ` Wei Liu
2014-04-29 13:27 ` [PATCH V7 net-next 7/7] xen-net{back, front}: Document multi-queue feature in netif.h Andrew J. Bennieston
2014-04-30 14:51 ` [PATCH V7 net-next 7/7] xen-net{back,front}: " Wei Liu
2014-04-30 16:47 ` Andrew Bennieston
2014-04-30 14:50 ` [PATCH V7 net-next] xen-net{back,front}: Multiple transmit and receive queues 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=536128CD.3010705@citrix.com \
--to=andrew.bennieston@citrix.com \
--cc=davem@davemloft.net \
--cc=david.vrabel@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=netdev@vger.kernel.org \
--cc=paul.durrant@citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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).