All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kent Overstreet <kent.overstreet@gmail.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH 1/3] Bcache: Version 6
Date: Sun, 04 Jul 2010 18:19:47 -0700	[thread overview]
Message-ID: <4C313333.8070507@gmail.com> (raw)
In-Reply-To: <20100704133434.fb23cc37.randy.dunlap@oracle.com>

On 07/04/2010 01:34 PM, Randy Dunlap wrote:
> On Sun, 4 Jul 2010 00:44:18 -0700 Kent Overstreet wrote:
>> +  make-bcache /dev/sde
>> +  echo "/dev/sde">  /sys/kernel/bcache/register_cache
>> +  echo "<UUID>  /dev/md1">  /sys/kernel/bcache/register_dev
>
> Hi,
>
> Where does one find 'make-bcache'?
> Maybe that info could be added here.

Yeah, that should be there -
git://evilpiepirate.org/~kent/bcache-tools.git

Added it to the documentation, probably well past time to add some 
documentation to the user space stuff too..

>> --- a/block/Kconfig
>> +++ b/block/Kconfig
>> @@ -77,6 +77,20 @@ config BLK_DEV_INTEGRITY
>>   	T10/SCSI Data Integrity Field or the T13/ATA External Path
>>   	Protection.  If in doubt, say N.
>>
>> +config BLK_CACHE
>> +	tristate "Block device as cache"
>> +	default m
>
> We try not to add (enable) non-core drivers to the kernel build.
> OTOH, in a year or a few, this could be a core driver.

Alright, turned that off.

It's certainly getting to be quite a lot of code, is there anything I 
can do to make it easier to look at? I really appreciate you taking the 
time.

      reply	other threads:[~2010-07-05  1:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-04  7:44 [RFC][PATCH 1/3] Bcache: Version 6 Kent Overstreet
2010-07-04  7:44 ` [RFC][PATCH 2/3] Bcache: Version 6 - The code Kent Overstreet
2010-07-04  7:44 ` [RFC][PATCH 3/3] Bcache: Version 6 - Hooks Kent Overstreet
2010-07-04 20:34 ` [RFC][PATCH 1/3] Bcache: Version 6 Randy Dunlap
2010-07-05  1:19   ` Kent Overstreet [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=4C313333.8070507@gmail.com \
    --to=kent.overstreet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.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.