From: Joe Thornber <thornber@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: gregkh@linuxfoundation.org
Subject: Re: [RFC] dm-writeboost: Porting daemon modulating migration from userland into the kernel
Date: Mon, 16 Sep 2013 10:21:35 +0100 [thread overview]
Message-ID: <20130916092134.GA20647@debian> (raw)
In-Reply-To: <5236C737.7040306@gmail.com>
On Mon, Sep 16, 2013 at 05:54:15PM +0900, Akira Hayakawa wrote:
> Hi, DM Guys,
>
> I am thinking of a little design change
> as to autonomous migration feature.
> I want to share this issue with you
> to first ask for your advice
> and for you to deeply understand the
> functionality of dm-writeboost at the same time.
I'm a bit confused. On the one hand you've asked for this to be
included in linux-next, yet on the other you're still making big
design changes.
When you first posted this code I said you'd need to get some people
behind it who are using this successfully. How far along this path
are you?
- Joe
next prev parent reply other threads:[~2013-09-16 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 8:54 [RFC] dm-writeboost: Porting daemon modulating migration from userland into the kernel Akira Hayakawa
2013-09-16 9:21 ` Joe Thornber [this message]
2013-09-16 10:13 ` Akira Hayakawa
2013-09-16 11:06 ` Joe Thornber
2013-09-16 11:49 ` Akira Hayakawa
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=20130916092134.GA20647@debian \
--to=thornber@redhat.com \
--cc=dm-devel@redhat.com \
--cc=gregkh@linuxfoundation.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.