From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Alex Zeffertt <alex.zeffertt@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 0/3] [linux-2.6.18-xen.hg] dom0 kernel support for xenstore stubdom
Date: Mon, 23 Mar 2009 16:57:14 +0000 [thread overview]
Message-ID: <C5ED6FEA.4BEC%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <49C7A89A.8020209@eu.citrix.com>
On 23/03/2009 15:19, "Alex Zeffertt" <alex.zeffertt@eu.citrix.com> wrote:
> Doing this offers the following two main advantages:
>
> 1. dom0 doesn't get scheduled on every xenbus access. This should make
> xenbus accesses speedier
> 2. this brings us closer to being able to reboot dom0 without needing to
> reboot all the VMs.
>
> Please consider these patches for inclusion in linux-2.6.18-xen.hg and
> xen-unstable.hg
Good stuff, but there'd have to be a really good reason to dump this in now
before 3.4 branches. I'll hold it for when the tree re-opens in a few weeks.
-- Keir
prev parent reply other threads:[~2009-03-23 16:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 15:19 [PATCH 0/3] [linux-2.6.18-xen.hg] dom0 kernel support for xenstore stubdom Alex Zeffertt
2009-03-23 16:57 ` Keir Fraser [this message]
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=C5ED6FEA.4BEC%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=alex.zeffertt@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.