xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad@darnok.org>
To: Shriram Rajagopalan <rshriram@cs.ubc.ca>
Cc: Brendan Cully <brendan@cs.ubc.ca>,
	xen-devel <xen-devel@lists.xensource.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: RFC: Still TODO for 4.2?
Date: Thu, 19 Jan 2012 16:42:27 -0400	[thread overview]
Message-ID: <20120119204227.GA3360@andromeda.dapyr.net> (raw)
In-Reply-To: <146BC0DC-6B03-4339-8172-A7C181E1AD06@cs.ubc.ca>

On Thu, Jan 19, 2012 at 11:00:19AM -0800, Shriram Rajagopalan wrote:
> On 2012-01-19, at 9:46 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
> 
> > On Thu, 2012-01-19 at 17:35 +0000, Shriram Rajagopalan wrote:
> >> 
> >> 
> >> I do have a set of initial patches for xl remus. Since the "script="
> >> support doesnt exist for disk configurations (required to support both
> >> DRBD and tapdisk backends).
> >> 
> >> So, currently I only have memory checkpointing functionality. No disk
> >> buffering.

Were the disk buffering implemented in kernel? As a dm-* device or
through blktap (which is not maintained)?

  reply	other threads:[~2012-01-19 20:42 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-17  9:09 RFC: Still TODO for 4.2? Jan Beulich
2012-01-19 16:35 ` Jan Beulich
2012-01-19 17:35   ` Shriram Rajagopalan
2012-01-19 17:46     ` Ian Campbell
2012-01-19 19:00       ` Shriram Rajagopalan
2012-01-19 20:42         ` Konrad Rzeszutek Wilk [this message]
2012-01-19 21:25           ` Shriram Rajagopalan
2012-01-19 21:10         ` Ian Campbell
2012-01-19 21:30           ` Shriram Rajagopalan
2012-01-19 21:39             ` Ian Campbell
     [not found] <mailman.456.1326725042.1471.xen-devel@lists.xensource.com>
2012-01-16 15:12 ` Andres Lagar-Cavilla
  -- strict thread matches above, loose matches on Subject: below --
2012-01-04 16:29 Ian Campbell
2012-01-04 16:47 ` Konrad Rzeszutek Wilk
2012-01-04 16:51   ` Stefano Stabellini
2012-01-16 13:42     ` Ian Campbell
2012-01-04 16:55 ` Jan Beulich
2012-01-16 13:39   ` Ian Campbell
2012-01-16 14:48     ` Jan Beulich
2012-01-16 15:00       ` Stefano Stabellini
2012-01-04 17:25 ` Pasi Kärkkäinen
2012-01-04 17:36   ` George Dunlap
2012-01-04 18:20   ` Tim Deegan
2012-01-05 10:39     ` Ian Campbell
2012-01-04 19:21   ` Wei Huang
2012-01-04 19:43     ` Pasi Kärkkäinen
2012-01-04 19:57       ` Wei Huang
2012-01-05  7:27         ` Pasi Kärkkäinen
2012-01-06 15:37         ` Konrad Rzeszutek Wilk
2012-01-06 19:08           ` Wei Huang
2012-02-06 17:57           ` Pasi Kärkkäinen
2012-01-05 13:19       ` Re : " David TECHER
2012-01-05 13:25         ` Ian Campbell
2012-01-05 13:41           ` Re : " David TECHER
2012-01-05 16:18             ` Ian Campbell
2012-01-16 13:28   ` Ian Campbell
2012-01-04 17:39 ` Roger Pau Monné
2012-01-05 17:49 ` Ian Jackson
2012-01-06 13:37   ` Ian Campbell
2012-01-10 16:06     ` Ian Jackson
2012-01-16 11:55 ` George Dunlap

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=20120119204227.GA3360@andromeda.dapyr.net \
    --to=konrad@darnok.org \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=brendan@cs.ubc.ca \
    --cc=rshriram@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 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).