From: Joe Thornber <thornber@redhat.com>
To: Akira Hayakawa <ruby.wktk@gmail.com>
Cc: snitzer@redhat.com, gregkh@linuxfoundation.org,
dm-devel@redhat.com, driverdev-devel@linuxdriverproject.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: writeboost: Add dm-writeboost
Date: Fri, 12 Dec 2014 14:24:48 +0000 [thread overview]
Message-ID: <20141212142447.GA30315@debian> (raw)
In-Reply-To: <548A39E7.80508@gmail.com>
On Fri, Dec 12, 2014 at 09:42:15AM +0900, Akira Hayakawa wrote:
> The SSD-caching should be log-structured.
No argument there, and this is why I've supported you with
dm-writeboost over the last couple of years.
However, after looking at the current code, and using it I think it's
a long, long way from being ready for production. As we've already
discussed there are some very naive design decisions in there, such as
copying every bio payload to another memory buffer, splitting all io
down to 4k. Think about the cpu overhead and memory consumption!
Think about how it will perform when memory is constrained and it
can't allocate many of those rambufs! I'm sure more issues will be
found if I read further.
I'm sorry to have disappointed you so, but if I let this go upstream
it would mean a massive amount of support work for me, not to mention
a damaged reputation for dm.
Mike raised the question of why you want this in the kernel so much?
You'd find none of the distros would support it; so it doesn't widen
your audience much. It's far better for you to maintain it outside of
the kernel at this point. Any users will be bold, adventurous people,
who will be quite capable of building a kernel module.
- Joe
next prev parent reply other threads:[~2014-12-12 14:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54883195.1060304@gmail.com>
[not found] ` <20141211152626.GA8196@redhat.com>
2014-12-12 0:42 ` [PATCH v2] staging: writeboost: Add dm-writeboost Akira Hayakawa
2014-12-12 9:12 ` [dm-devel] " Bart Van Assche
2014-12-12 9:35 ` Akira Hayakawa
2014-12-12 11:41 ` Bart Van Assche
2014-12-12 14:24 ` Joe Thornber [this message]
2014-12-12 15:09 ` Akira Hayakawa
2014-12-13 6:45 ` [dm-devel] " Jianjian Huo
2014-12-13 14:07 ` Akira Hayakawa
2014-12-14 2:12 ` Akira Hayakawa
2014-12-14 2:46 ` Jianjian Huo
2014-12-14 3:22 ` Akira Hayakawa
2014-12-14 3:00 ` 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=20141212142447.GA30315@debian \
--to=thornber@redhat.com \
--cc=dm-devel@redhat.com \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ruby.wktk@gmail.com \
--cc=snitzer@redhat.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