linux-kernel - Re: [PATCH v3] staging: writeboost: Add dm-writeboost

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 17 Jan 2015 16:09:52 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Akira Hayakawa <ruby.wktk@...il.com>
Cc:	snitzer@...hat.com, ejt@...hat.com, dm-devel@...hat.com,
	driverdev-devel@...uxdriverproject.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] staging: writeboost: Add dm-writeboost

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@...il.com>

I need an ack from a dm developer before I can take this.

thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/