From: Vincent Hanquez <vincent.hanquez@eu.citrix.com>
To: Keir Fraser <Keir.Fraser@eu.citrix.com>
Cc: "Łukasz Oleś" <lukaszoles@gmail.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Re: oxenstored in stubdom ?
Date: Sun, 22 Aug 2010 10:14:10 +0100 [thread overview]
Message-ID: <4C70EA62.8000807@eu.citrix.com> (raw)
In-Reply-To: <C8969CF6.1EB2E%keir.fraser@eu.citrix.com>
On 22/08/10 09:23, Keir Fraser wrote:
> On 22/08/2010 08:34, "Vincent Hanquez"<vincent.hanquez@eu.citrix.com>
> wrote:
>
>>> So.. having xenstore in separate domain can have other advantages
>>> (performance?).
>>> Is it (or will be) possible run oxenstroed in stubdomain?
>>
>> oxenstored is already restartable (or used to be and easy to fix if it
>> was broken), so from a xenstore point of view, you could already restart
>> dom0; Obviously this would block all the domains that try to do a
>> xenstore query, but if the dom0 is restarted quickly enough this
>> shouldn't be too noticeable since a normal working domain shouldn't use
>> much xenstore after starting up.
>
> So that's "very probably restartable" then? ;-)
well yes, "very probably" is pretty good odds i think. :p
more seriously, it depends from which perspective you're looking at the
dom0 restart problem. But according to previous experience during
oxenstored development, i'm pretty sure that oxenstored would cope and
that most of the problems are elsewhere in the stack. moving oxenstored
to a stubdomain is almost orthogonal (roughly 89 degrees.)
--
Vincent
next prev parent reply other threads:[~2010-08-22 9:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-21 22:39 oxenstored in stubdom ? Łukasz Oleś
2010-08-22 7:34 ` Vincent Hanquez
2010-08-22 8:23 ` Keir Fraser
2010-08-22 9:14 ` Vincent Hanquez [this message]
2010-08-22 9:44 ` Keir Fraser
2010-08-22 19:18 ` Łukasz Oleś
2010-08-22 19:37 ` Keir Fraser
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=4C70EA62.8000807@eu.citrix.com \
--to=vincent.hanquez@eu.citrix.com \
--cc=Keir.Fraser@eu.citrix.com \
--cc=lukaszoles@gmail.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 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).