mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Akira Hayakawa <ruby.wktk@gmail.com>
To: gregkh@linuxfoundation.org, snitzer@redhat.com, agk@redhat.com
Cc: linux-kernel@vger.kernel.org, dm-devel@redhat.com
Subject: Re: [PATCH] staging: writeboost: Add dm-writeboost
Date: Mon, 08 Dec 2014 06:04:41 +0900	[thread overview]
Message-ID: <5484C0E9.3060707@gmail.com> (raw)
In-Reply-To: <20141207200834.GA2322@kroah.com>

> Greg Kroah-Hartman <gregkh@linuxfoundation.org> please, and also the
> driverdevel mailing list, which is where the rest of the staging patches
> go.
Sorry and yes, I will fix.

> And, I'll need an ack from the dm maintainers before I can accept this
> as something they think is ok and will get merged to the "real" part of
> the kernel someday.
OK.

Mike and Alasdair,
I need your ack

- Akira

On 12/8/14 5:08 AM, Greg KH wrote:
> On Sun, Dec 07, 2014 at 09:35:26PM +0900, Akira Hayakawa wrote:
>> --- /dev/null
>> +++ b/drivers/staging/writeboost/TODO
>> @@ -0,0 +1,47 @@
>> +TODO:
>> +
>> +- Expose bugs and fix them.
>> +- Clean up the interfaces. Some input values should be limited in case user may choose too big values.
>> +- Wait for proper review by Mike Snitzer.
>> +- Fix up documents.
>> +
>> +-------------------------------------------------------------------------
>> +
>> +Project Ideas:
>> +
>> +1. Add read caching feature
>> +Device-Mapper maintainer Mike Snitzer said that
>> +a single target should provide caching for both reads and writes.
>> +(cf. http://www.redhat.com/archives/dm-devel/2014-January/msg00078.html)
>> +
>> +To follow Mike's guide, I will implement read-caching for Writeboost.
>> +The great idea is, at least conceptually,
>> +sending back the read data to the write entrance.
>> +I didn't notice this simple idea at that time of previous discussion.
>> +
>> +This should be done background and
>> +some threshold to determine
>> +which sequence of data should be staged.
>> +
>> +This feature will be implemented step-by-step.
>> +I don't think this feature will change then interface drastically.
>> +
>> +2. Improve initialization time
>> +Some user complains that the initialization is too slow.
>> +
>> +Any ideas?
>> +
>> +3. Reduce metadata footprint
>> +Writeboost has a hash table in RAM for cache management.
>> +This isn't cheap.
>> +
>> +Any ideas?
>> +
>> +-------------------------------------------------------------------------
>> +
>> +Please send any patches
>> +To:
>> +Akira Hayakawa <ruby.wktk@gmail.com>
>> +Cc:
>> +Greg Kroah-Hartman <greg@kroah.com>
> 
> Greg Kroah-Hartman <gregkh@linuxfoundation.org> please, and also the
> driverdevel mailing list, which is where the rest of the staging patches
> go.
> 
> And, I'll need an ack from the dm maintainers before I can accept this
> as something they think is ok and will get merged to the "real" part of
> the kernel someday.
> 
> thanks,
> 
> greg k-h
> 


  reply	other threads:[~2014-12-07 21:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-07 12:35 Akira Hayakawa
2014-12-07 20:08 ` Greg KH
2014-12-07 21:04   ` Akira Hayakawa [this message]
2014-12-09 15:12     ` [dm-devel] " Joe Thornber
2014-12-09 15:48       ` Mike Snitzer
2014-12-10 10:21         ` Akira Hayakawa
2014-12-10 10:00       ` [dm-devel] [PATCH] " Joe Thornber
2014-12-10 11:00         ` Akira Hayakawa
2014-12-10 11:22           ` Joe Thornber
2014-12-10 12:33           ` Joe Thornber
2014-12-10 12:59             ` Akira Hayakawa
2014-12-10 13:13               ` Joe Thornber
2014-12-10 13:31                 ` Akira Hayakawa
2014-12-10 13:42                   ` Joe Thornber
2014-12-10 14:43                     ` Akira Hayakawa
2014-12-12 12:51         ` Marian Csontos

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=5484C0E9.3060707@gmail.com \
    --to=ruby.wktk@gmail.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --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

Powered by JetHome