From: Ian Campbell <ian.campbell@citrix.com>
To: Mike Latimer <mlatimer@suse.com>, xen-devel@lists.xen.org
Subject: Re: Shared image files and block script performance
Date: Tue, 29 Sep 2015 10:25:32 +0100 [thread overview]
Message-ID: <1443518732.16718.16.camel@citrix.com> (raw)
In-Reply-To: <7906712.vmDJM0hI90@mlatimer1.dnsdhcp.provo.novell.com>
On Mon, 2015-09-28 at 17:14 -0600, Mike Latimer wrote:
> Any better options or ideas?
Is part of the problem that shell is a terrible choice for this kind of
check?
Would shelling out to a helper utility allow this to be written in
something better?
I think we'd still be constrained in the languages used, probably it would
have to be C to avoid adding dependencies on additional runtimes or
compilers, but that might be good enough to allow us to minimise the number
of times we need to go through the database. If nothing else it would make
it possible to use actual datastructures, locking, XS transactions etc.
Ian.
next prev parent reply other threads:[~2015-09-29 9:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 23:14 Shared image files and block script performance Mike Latimer
2015-09-29 9:25 ` Ian Campbell [this message]
2015-09-29 21:18 ` Mike Latimer
2015-09-30 10:35 ` Ian Campbell
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=1443518732.16718.16.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=mlatimer@suse.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.