Linux bcache driver list
 help / color / mirror / Atom feed
From: Cory Coager <ccoager-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Kent Overstreet
	<kent.overstreet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: support for physical ramdisk
Date: Wed, 19 Jan 2011 22:34:05 -0500	[thread overview]
Message-ID: <4D37AD2D.6070108@gmail.com> (raw)
In-Reply-To: <AANLkTin+xKeYbxSU6u=h8bfujSpm3fxqurC0nR4+89wX-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Sounds great, when will it be ready? ;-)

On 01/19/2011 08:27 PM, Kent Overstreet wrote:
> Well, ram is more expensive per gigabyte than SSDs, particularly if
> you've got something with a battery attached - the idea would be to
> use your SSD for buffering 80 gb or so of writes, but then buffer all
> of bcache's metadata writes in battery backed-up ram, significantly
> decreasing the number of write IOPS to the SSD, and making it so
> pretty much all the writes to the SSD are big contiguous writes.
--
To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2011-01-20  3:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-20  0:10 support for physical ramdisk Cory Coager
     [not found] ` <4D377D66.5020609-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-01-20  0:22   ` Kent Overstreet
     [not found]     ` <AANLkTik30_V_bWGsvoUQw-5-W7URK1tSTDSfcTa8LayX-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-01-20  0:59       ` Cory Coager
     [not found]         ` <AANLkTinUD1_z3iZ3VgJFh=JkF+6EWDq62==Z9EhBpwBP@mail.gmail.com>
     [not found]           ` <AANLkTinUD1_z3iZ3VgJFh=JkF+6EWDq62==Z9EhBpwBP-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-01-20  1:14             ` Cory Coager
     [not found]               ` <4D378C5E.7050309-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-01-20  1:27                 ` Kent Overstreet
     [not found]                   ` <AANLkTin+xKeYbxSU6u=h8bfujSpm3fxqurC0nR4+89wX-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-01-20  3:34                     ` Cory Coager [this message]
     [not found]                       ` <4D37AD2D.6070108-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-01-20  3:52                         ` Kent Overstreet

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=4D37AD2D.6070108@gmail.com \
    --to=ccoager-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=kent.overstreet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /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