From: NeilBrown <neilb@suse.de>
To: Roberto Spadim <roberto@spadim.com.br>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: RAID0 - cache
Date: Thu, 20 Jan 2011 07:20:16 +1100 [thread overview]
Message-ID: <20110120072016.1b2162c8@notabene.brown> (raw)
In-Reply-To: <AANLkTik7xBOYVgZJC0sStpK=oPHdX53XzwYC5CVDKy_v@mail.gmail.com>
On Wed, 19 Jan 2011 18:13:23 -0200 Roberto Spadim <roberto@spadim.com.br>
wrote:
> Hi guys, from a long email i will start this one: (the last one wasn´t send)
>
> think about this:
>
> /dev/sda (sata disk 1000gb size, latency of 1ms to move head, 100mb/s
> to write/read)
> /dev/sdb (ssd 1gb size, latency of <100us to find what flash and
> position, 500mb/s to write/read)
> ram memory (8gb size, with 1gb not used)
> /dev/mdxxx (the new device i´m calling it as raid0-cache)
>
> how raid0-cache work?
>
>
> how to create raid?
> tell what the sequencial read cache estrategy:
> memory(tell fixed memory size) - /dev/sdb - /dev/sda - another device
> (maybe just 2 is suficiente /dev/sdb and /dev/sda)...
>
>
> how to read?
> first, read from the first read device (memory)
> if information not there -> read from second read device (/dev/sdb),
> update information at first read device, return the read value
> if information not there -> read from third read device (/dev/sda),
> update information at second and first read device, return the read
> value
>
> how to write?
> flush space from first read device to second read device
> write to first read device, return OK
>
> background thread:
> sync from first write device (memory) to second write device (/dev/sdb)
> flush from second write device (/dev/sdb) to third write device (/dev/sda)
>
> startup:
> using cache:
> flush everythink from first write device (memory) to second write
> device (/dev/sdb)
> flush everythink from second write device (/dev/sdb) to second write
> device (/dev/sda)
> since memory is volatille, at startup it can´be flushed...
> without cache:
> make first write device unusable (memory)
> make second write device unusable
> here we can have write problems, since a wrong power off, can lost
> information from cache (first and second write device)
>
>
>
> anyidea who can make it?
"Hey, I've got this clever idea, I wish someone would implement it" almost
always results in ... nothing.
People with the ability to implement are much more interested in implementing
their own ideas.
But see also "bcache".
NeilBrown
> thanks
> --
> Roberto Spadim
> Spadim Technology / SPAEmpresarial
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-01-19 20:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 20:13 RAID0 - cache Roberto Spadim
2011-01-19 20:20 ` NeilBrown [this message]
2011-01-19 21:35 ` Roberto Spadim
2011-01-19 21:41 ` Roberto Spadim
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=20110120072016.1b2162c8@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=roberto@spadim.com.br \
/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.