From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Brendan Cully <brendan@cs.ubc.ca>
Cc: andy@cs.ubc.ca, xen-devel@lists.xensource.com
Subject: Re: [PATCH 0 of 3] Remus: control tool
Date: Fri, 13 Nov 2009 09:18:59 -0500 [thread overview]
Message-ID: <20091113141859.GB23952@phenom.dumpdata.com> (raw)
In-Reply-To: <patchbomb.1258074621@zanzibar.lan>
On Thu, Nov 12, 2009 at 05:10:21PM -0800, Brendan Cully wrote:
> The following patch series integrates the Remus control layer into
> Xen. It provides a single user-visible script ("remus") to activate
> Remus on a guest virtual machine, and the libraries required by that
> script.
Cool. Looking forward to read them.
>
> Network buffering requires the linux IMQ (http://linuximq.net) patch
> to be applied to dom0. I'll mail the upstream version that applies to
> the linux-2.6.18-xen.hg tree separately.
Is there a 2.6.31.x variant of the code? Are there plans to submit the
patches to LKML?
next prev parent reply other threads:[~2009-11-13 14:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 1:10 [PATCH 0 of 3] Remus: control tool Brendan Cully
2009-11-13 1:10 ` [PATCH 1 of 3] Remus: add python control extensions Brendan Cully
2009-11-13 1:10 ` [PATCH 2 of 3] Remus: add control script to activate remus on a VM Brendan Cully
2009-11-13 1:10 ` [PATCH 3 of 3] Remus: support for network buffering Brendan Cully
2009-11-13 14:18 ` Konrad Rzeszutek Wilk [this message]
2009-11-13 21:36 ` [PATCH 0 of 3] Remus: control tool Brendan Cully
2009-12-01 15:20 ` Pasi Kärkkäinen
2009-12-01 16:16 ` Brendan Cully
2009-12-01 23:04 ` Jeremy Fitzhardinge
2009-12-01 23:53 ` Brendan Cully
2009-12-02 8:07 ` Keir Fraser
2009-12-02 18:17 ` Jeremy Fitzhardinge
2009-12-02 18:20 ` Brendan Cully
2009-12-02 18:30 ` Jeremy Fitzhardinge
2009-12-02 18:25 ` Keir Fraser
2009-12-02 18:34 ` Jeremy Fitzhardinge
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=20091113141859.GB23952@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=andy@cs.ubc.ca \
--cc=brendan@cs.ubc.ca \
--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.