All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Fehlig <jfehlig@novell.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] xend: drbd improvements
Date: Thu, 13 Jan 2011 08:59:04 -0700	[thread overview]
Message-ID: <4D2F2148.6060504@novell.com> (raw)
In-Reply-To: <19758.58834.718990.325579@mariner.uk.xensource.com>

Ian Jackson wrote:
> Jim Fehlig writes ("Re: [Xen-devel] [PATCH] xend: drbd improvements"):
>   
>> Have you had a chance to test my suggestion above (reverting c/s 19444
>> and using the xend patch we have in SuSE)?  It has been working well for
>> us, but another "Tested-by:" may convince upstream to take these changes
>> as well.  Perhaps it is too late for 4.1 as we're at RC2 already.
>>     
>
> I'd love to have another test report.

Shriram reported that he successfully tested these changes.

>   I didn't apply these patches
> because it wasn't clear to me exactly what the proposed changes were
> and, as you say, that they had been sufficiently tested.
>   

The revert of c/s 19444 simply removes more 'drbd' cruft from xend
internals.

As for my xend patch, is the commit message that vague?

-------------------------
xend: improve psudeo-bootloader support for external block scripts

Userspace tools support external block scripts (e.g. block-drbd
provided by drbd project). The psuedo-bootloader setup code in
xend has a few limitations wrt external block scripts, which this
patch addresses.

blkif.py: parse_uname() utility function should be able to parse a
disk specifier understood by the rest of the tools.

XendDomainInfo.py: Block devices using external block scripts must
be attached to dom0 before running the psuedo-bootloader.
-------------------------

I can improve it if need be.

Regards,
Jim

  reply	other threads:[~2011-01-13 15:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-09 17:50 [PATCH] xend: drbd improvements Jim Fehlig
2010-11-09 18:26 ` Ian Jackson
2010-11-09 22:21   ` Jim Fehlig
2010-11-10 17:49     ` Jim Fehlig
2010-12-17  0:45       ` Jim Fehlig
2010-12-17  0:58         ` Shriram Rajagopalan
2010-12-17  3:46           ` Jim Fehlig
2011-01-05 23:32         ` Ian Jackson
2011-01-06 17:48           ` Shriram Rajagopalan
2011-01-10 23:31             ` Jim Fehlig
2011-01-13  3:38               ` Jim Fehlig
2011-01-13  7:36                 ` Shriram Rajagopalan
2011-01-13 11:45                 ` Ian Jackson
2011-01-13 15:59                   ` Jim Fehlig [this message]
2011-01-18 17:24               ` Ian Jackson

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=4D2F2148.6060504@novell.com \
    --to=jfehlig@novell.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --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 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.