From: Akira Hayakawa <ruby.wktk@gmail.com>
To: 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 20:49:03 +0900 [thread overview]
Message-ID: <5236F02F.2040609@gmail.com> (raw)
In-Reply-To: <20130916110647.GA23933@debian>
Joe,
> Is anyone using your new target other than you? You've posted on
> dm-devel, you've posted on lkml, has anyone bothered to try it?
Unfortunately, the answer is NO.
Some Japanese kernel developers once tried to use it
but didn't reached operation eventually.
But, I am feeling dm-writeboost gathering attention from storage engineers.
That I can not get 3rd party users right now is not because dm-writeboost is trivial.
I believe the target is worth merging in the future.
For example, dm-writeboost is discussed in the Russian website below
http://www.opennet.ru/opennews/art.shtml?num=37864
AND
also in Phoronix
http://phoronix.com/forums/showthread.php?84073-A-New-Log-Structured-Linux-Caching-Software-Driver#post354983
My conclusion is
there are potential users and I think I can greet them as users trying dm-writeboost
if the target is staged.
This issue of porting the userland daemon to in-kernel
is for them to use software of my best efforts.
If the design issue is raised again after all, all I can do it to nothing but fix it.
My regret is that I should have fixed this issue before proposal to staging tree.
PythonDaemon module being unstable was already found before that
although I didn't consider the design is bad.
Akira
prev parent reply other threads:[~2013-09-16 11:49 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
2013-09-16 10:13 ` Akira Hayakawa
2013-09-16 11:06 ` Joe Thornber
2013-09-16 11:49 ` Akira Hayakawa [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=5236F02F.2040609@gmail.com \
--to=ruby.wktk@gmail.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.