Linux bcache driver list
 help / color / mirror / Atom feed
From: Dave Jiang <dave.jiang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Jack Wang <jack.wang.usish-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: John McCabe-Dansted
	<gmatht-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	C Sights <csights-97jfqw80gc6171pxa8y+qA@public.gmane.org>,
	linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	jack_wang-aA8Fybl81pAAvxtiuMwx3w@public.gmane.org,
	lindar_liu-aA8Fybl81pAAvxtiuMwx3w@public.gmane.org
Subject: Re: bcache compared to more RAM
Date: Thu, 16 Aug 2012 09:20:48 -0700	[thread overview]
Message-ID: <502D1DE0.8090300@intel.com> (raw)
In-Reply-To: <CA+res+RTJDPKS02Pou8Pui0qnCX1=L6juS1k5mYJ-bp-Qd+JmA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Wed 15 Aug 2012 08:29:38 PM MST, Jack Wang wrote:
> 2012/8/16 Dave Jiang <dave.jiang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>:
>> On 08/15/2012 04:51 AM, John McCabe-Dansted wrote:
>>> On Wed, Aug 15, 2012 at 7:30 PM, C Sights <csights-97jfqw80gc6171pxa8y+qA@public.gmane.org> wrote:
>>>> Hi all,
>>>>    Has anyone tried creating a bcache device in RAM and benchmarking
>>>> performance of that versus just allowing that RAM to be used as file system
>>>> buffers?
>>> I doubt it; bcache is designed to use non-volatile flash memory rather
>>> than ram.
>>>
>>> If the filesystem is readonly, I imagine that using RAM for bcache
>>> would lead to worse performance as it would just add overhead. If the
>>> filesystem is read-write then it might lead to better performance but
>>> would also lead to the file-system being trashed on if unexpected
>>> power loss occurs.
>>>
>>> Under what circumstance would you intend to actually use ram backed bcache?
>>>
>>
>> So the Intel Xeon E5-2600 series platforms has this feature called
>> asynchronous DRAM refresh (ADR). Essentially it's battery backed DRAM on
>> per DIMM socket basis. I have written a RAM disk driver on top of that
>> experimentally and played a little bit with it used by bcache instead of
>> SSD. Writing to the memory region isn't going to be as fast as normal
>> cached RAM because you have to ensure the data is flushed to the DRAM.
>> However, read should be the same as cached DRAM. But the writing should
>> still be faster than SSD. Anyhow, I'm more curious as to how I can
>> benchmark this to demonstrate if this is a benefit with bcache. i.e.
>> what benchmarking tool(s) I should use and with what parameters etc.
>>
> Hi Dave,
>
> Intesting, wish to see the result. what cache mode is intended to use with ADR.
>
> Jack
> --

Jack,
Right now I'm using wb mode for cache. However when I write I call 
clflush_cache_range() and then read the last dword to make really sure 
that everything has made it to the DRAM. I do wish it's possible on IA 
to just flush without invalidate the cache though.

  parent reply	other threads:[~2012-08-16 16:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-15 11:30 bcache compared to more RAM C Sights
     [not found] ` <201208150630.36861.csights-97jfqw80gc6171pxa8y+qA@public.gmane.org>
2012-08-15 11:51   ` John McCabe-Dansted
2012-08-15 16:23     ` Dave Jiang
     [not found]       ` <502BCD0C.6080108-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2012-08-16  2:29         ` Joseph Glanville
2012-08-16  3:29         ` Jack Wang
     [not found]           ` <CA+res+RTJDPKS02Pou8Pui0qnCX1=L6juS1k5mYJ-bp-Qd+JmA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-08-16 16:20             ` Dave Jiang [this message]
     [not found]               ` <502D1DE0.8090300-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2012-08-17  1:31                 ` C Sights

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=502D1DE0.8090300@intel.com \
    --to=dave.jiang-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=csights-97jfqw80gc6171pxa8y+qA@public.gmane.org \
    --cc=gmatht-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=jack.wang.usish-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=jack_wang-aA8Fybl81pAAvxtiuMwx3w@public.gmane.org \
    --cc=lindar_liu-aA8Fybl81pAAvxtiuMwx3w@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