From: Cory Coager <ccoager@gmail.com>
To: Roberto Spadim <roberto@spadim.com.br>
Cc: linux-raid@vger.kernel.org
Subject: Re: support for external persistent cache
Date: Wed, 19 Jan 2011 10:52:11 -0500 [thread overview]
Message-ID: <20110119155211.GA31671@erebus.underworld.local> (raw)
In-Reply-To: <AANLkTi=5rNxQtNsixdSYZE_XBtQR+q=WpwA_BNXp5vpr@mail.gmail.com>
On Wed, Jan 19, 2011 at 01:19:18PM -0200, Roberto Spadim wrote:
> ok,
> but if you don?t sync file system (remove from memory and put in disk
> controller)
> you will lost information with or without a batery
>
> how to don?t lose information?
> don?t power down you memory,cpu, disk controller (sata controler, raid
> controller, or anyother) and disks (does it have a batery? a super
> capacitor?)
> if you power down, be sure that all memory was send to disk controller
> and that disk controller have energy (batery or capacitor) to send
> information to disks (they need batery or capacitor too)
>
> right?
> so, a ups can power cpu, memory, disk controller and disks with only
> one batery (not a batery for each device cpu,memory,disk,disk
> controller)
> the best world could be a non volatile memory (250mb/s flash 4kb
> block) with the speed of volatile memory (10000mb/s ddr3 i don?t know
> the block size)
It would have to work the same as a hardware RAID controller.
Information is first written to the cache then synced to the
disk. If the data is in the cache but not on the disk, the
machine loses power, next boot up the software raid would need a
way to flush the data from the ram disk to the disk. Of course
this would require the battery be in working condition, as with
any hardware.
Hopefully I've explained that well enough. Perhaps it will be
better to see the hardware I'm talking about:
http://techreport.com/articles.x/16255
next prev parent reply other threads:[~2011-01-19 15:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 3:06 support for external persistent cache Cory Coager
2011-01-19 3:12 ` Roberto Spadim
2011-01-19 3:17 ` Roberto Spadim
2011-01-19 3:34 ` Cory Coager
2011-01-19 15:19 ` Roberto Spadim
2011-01-19 15:52 ` Cory Coager [this message]
2011-01-19 16:16 ` Roberto Spadim
2011-01-19 16:17 ` Roberto Spadim
2011-01-19 16:20 ` Roberto Spadim
2011-01-19 16:29 ` Cory Coager
2011-01-19 16:44 ` Roberto Spadim
2011-01-19 16:57 ` Roberto Spadim
2011-01-19 17:04 ` Roberto Spadim
2011-01-19 17:19 ` Cory Coager
2011-01-19 17:22 ` Roberto Spadim
2011-01-19 17:02 ` Cory Coager
2011-01-19 17:09 ` Roberto Spadim
2011-01-19 17:15 ` Roberto Spadim
2011-01-19 17:20 ` Roberto Spadim
2011-01-19 17:29 ` Cory Coager
2011-01-19 17:37 ` 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=20110119155211.GA31671@erebus.underworld.local \
--to=ccoager@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).