From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Jim Fehlig <jfehlig@novell.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>, Ryan O'Connor <rjo@cs.ubc.ca>
Subject: Re: regression with c/s 21223
Date: Fri, 7 May 2010 20:41:03 +0100 [thread overview]
Message-ID: <C80A2B5F.185E%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4BE46A75.8010207@novell.com>
On 07/05/2010 20:31, "Jim Fehlig" <jfehlig@novell.com> wrote:
>> I suppose it really just punts
>> the tap2 issues, unless we also get rid of the tap2-falls-back-to-tap1
>> logic?
>>
>
> It reverts 2 hunks of c/s 19874, which implicitly converts the device to
> tap2 in a xend client app! If the same configuration is provided to
> xend through libvirt, this implicit conversion does not occur. I'd
> suspect this is true for direct users of XenAPI as well.
>
> But yes, I agree that if an explicit differentiation between tap and
> tap2 exists, then the tap2-fall-back-to-tap1 logic should be removed.
> It would be nice to get input from others, particularly authors of
> blktap2 integration patches :-).
Well, in the absence of that I'm happy to take the patch, and I guess
backport it for 4.0.1.
-- Keir
next prev parent reply other threads:[~2010-05-07 19:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 3:36 regression with c/s 21223 Jim Fehlig
2010-05-07 8:30 ` Keir Fraser
2010-05-07 13:37 ` Jim Fehlig
2010-05-07 18:12 ` Keir Fraser
2010-05-07 19:31 ` Jim Fehlig
2010-05-07 19:41 ` Keir Fraser [this message]
2010-05-16 10:54 ` Does Xen 3.4.3 support pvops kernel 2.6.32.12 ? Boris Derzhavets
2010-05-16 11:09 ` Keir Fraser
2010-05-16 12:11 ` Joanna Rutkowska
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=C80A2B5F.185E%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=jfehlig@novell.com \
--cc=rjo@cs.ubc.ca \
--cc=xen-devel@lists.xensource.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).