From: Greg KH <gregkh@linuxfoundation.org>
To: Akira Hayakawa <ruby.wktk@gmail.com>
Cc: ejt@redhat.com, driverdev-devel@linuxdriverproject.org,
dm-devel@redhat.com, snitzer@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] staging: writeboost: Add dm-writeboost
Date: Sat, 17 Jan 2015 16:09:52 -0800 [thread overview]
Message-ID: <20150118000952.GB26160@kroah.com> (raw)
In-Reply-To: <54A508F7.1020207@gmail.com>
On Thu, Jan 01, 2015 at 05:44:39PM +0900, Akira Hayakawa wrote:
> This patch adds dm-writeboost to staging tree.
>
> dm-writeboost is a log-structured SSD-caching driver.
> It caches data in log-structured way on the cache device
> so that the performance is maximized.
>
> The merit of putting this driver in staging tree is
> to make it possible to get more feedback from users
> and polish the codes.
>
> v2->v3
> - rebased onto 3.19-rc2
> - Add read-caching support (disabled by default)
> Several tests are pushed to dmts.
> - An critical bug fix
> flush_proc shouldn't free the work_struct it's running on.
> I found this bug while I am testing read-caching.
> I am not sure why i didn't exhibit before but it's truly a bug.
> - Fully revised the README.
> Now that we have read-caching support, the old README was completely obsolete.
> - Update TODO
> Implementing read-caching is done.
> - bump up the copyright year to 2015
> - fix up comments
>
>
> Signed-off-by: Akira Hayakawa <ruby.wktk@gmail.com>
I need an ack from a dm developer before I can take this.
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Akira Hayakawa <ruby.wktk@gmail.com>
Cc: snitzer@redhat.com, ejt@redhat.com, dm-devel@redhat.com,
driverdev-devel@linuxdriverproject.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] staging: writeboost: Add dm-writeboost
Date: Sat, 17 Jan 2015 16:09:52 -0800 [thread overview]
Message-ID: <20150118000952.GB26160@kroah.com> (raw)
In-Reply-To: <54A508F7.1020207@gmail.com>
On Thu, Jan 01, 2015 at 05:44:39PM +0900, Akira Hayakawa wrote:
> This patch adds dm-writeboost to staging tree.
>
> dm-writeboost is a log-structured SSD-caching driver.
> It caches data in log-structured way on the cache device
> so that the performance is maximized.
>
> The merit of putting this driver in staging tree is
> to make it possible to get more feedback from users
> and polish the codes.
>
> v2->v3
> - rebased onto 3.19-rc2
> - Add read-caching support (disabled by default)
> Several tests are pushed to dmts.
> - An critical bug fix
> flush_proc shouldn't free the work_struct it's running on.
> I found this bug while I am testing read-caching.
> I am not sure why i didn't exhibit before but it's truly a bug.
> - Fully revised the README.
> Now that we have read-caching support, the old README was completely obsolete.
> - Update TODO
> Implementing read-caching is done.
> - bump up the copyright year to 2015
> - fix up comments
>
>
> Signed-off-by: Akira Hayakawa <ruby.wktk@gmail.com>
I need an ack from a dm developer before I can take this.
thanks,
greg k-h
next prev parent reply other threads:[~2015-01-18 0:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 8:44 [PATCH v3] staging: writeboost: Add dm-writeboost Akira Hayakawa
2015-01-18 0:09 ` Greg KH [this message]
2015-01-18 0:09 ` Greg KH
2015-02-20 8:44 ` Akira Hayakawa
2015-02-20 8:44 ` Akira Hayakawa
2015-02-20 15:06 ` Joe Thornber
2015-02-20 15:25 ` Akira Hayakawa
2015-02-20 15:50 ` Joe Thornber
2015-02-20 16:06 ` Akira Hayakawa
2015-02-20 16:17 ` Joe Thornber
2015-02-21 1:36 ` Akira Hayakawa
2015-02-21 1:36 ` 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=20150118000952.GB26160@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dm-devel@redhat.com \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=ejt@redhat.com \
--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 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.