From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Mike Latimer <mlatimer@suse.com>
Cc: George.Dunlap@eu.citrix.com, stefano.stabellini@eu.citrix.com,
wei.liu2@citrix.com, roger.pau@citrix.com,
xen-devel@lists.xen.org
Subject: Re: [PATCH v3 1/1] tools/hotplug: Scan xenstore once when attaching shared images files
Date: Wed, 7 Oct 2015 12:52:02 +0100 [thread overview]
Message-ID: <1444218722.1410.19.camel@citrix.com> (raw)
In-Reply-To: <22034.43037.80464.987570@mariner.uk.xensource.com>
On Mon, 2015-10-05 at 17:41 +0100, Ian Jackson wrote:
> Mike Latimer writes ("[PATCH v3 1/1] tools/hotplug: Scan xenstore once
> when attaching shared images files"):
> > During the attachment of a loopback mounted image file, the mode of all
> > curent instances of this device already attached to other domains must
> > be
> > checked. This requires finding all loopback devices pointing to the
> > inode
> > of the shared image file, and then comparing the major and minor number
> > of
> > these devices to the major and minor number of every vbd device found
> > in the
> > xenstore database.
> >
> > Prior to this patch, the entire xenstore database is walked for every
> > instance
> > of every loopback device pointing to the same shared image file. This
> > process
> > causes the block attachment process to becomes exponentially slower
> > with every
> > additional attachment of a shared image.
> >
> > Rather than scanning all of xenstore for every instance of a shared
> > loopback
> > device, this patch creates a list of the major and minor numbers from
> > all
> > matching loopback devices. After generating this list, Xenstore is
> > walked
> > once, and major and minor numbers from every vbd are checked against
> > the list.
> > If a match is found, the mode of that vbd is checked for compatibility
> > with
> > the mode of the device being attached.
>
> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
Applied.
Mike, FWIW for singleton patches it is normally ok to dispense with the 0/1
mail and to just send the patch by itself. If there is commentary which
doesn't belong in the commit message you can put it below a "---" marker
(and "git am" will strip it). If there is lots commentary then sending a
0/1 is fine if you want, of course.
Ian.
next prev parent reply other threads:[~2015-10-07 11:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 14:09 [PATCH v3 0/1] Block script performance with shared image files Mike Latimer
2015-10-02 14:09 ` [PATCH v3 1/1] tools/hotplug: Scan xenstore once when attaching shared images files Mike Latimer
2015-10-05 16:41 ` Ian Jackson
2015-10-07 11:52 ` Ian Campbell [this message]
2015-10-07 15:25 ` Mike Latimer
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=1444218722.1410.19.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=mlatimer@suse.com \
--cc=roger.pau@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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.