From: Roberto Spadim <roberto@spadim.com.br>
To: Cory Coager <ccoager@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: support for external persistent cache
Date: Wed, 19 Jan 2011 01:17:31 -0200 [thread overview]
Message-ID: <AANLkTim3BJVbHdtByAni2ObUf0Qjece9jkd1_MSkT56P@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimTnaHEA0+==hs7Ew0Zzvdr1EOtxEqH=EfgdN-7@mail.gmail.com>
reading again... should you use a good ups system with information
about % of batery, like a notebook?
read/write cache can be change with async or sync options on filesystem mount
batery support is done with ups system
maybe with some time of use (10 years) the baterry of you ramdisk
should be replaced, will you replace it? is easier replace a ups
batery or a ramdisk specific batery?
check at internet about 12vdc atx power supply, and use a charger and
a car batery to supply power to your computer, it's a very nice
solution =)
2011/1/19 Roberto Spadim <roberto@spadim.com.br>:
> i think that is a fileystem cache
> not a md raid cache
> i'm right?
>
> 2011/1/19 Cory Coager <ccoager@gmail.com>:
>> I was wondering if it would be possible to add support for specifying a
>> device to use for read/write persistent cache. The reason why I'm asking is
>> because I see physical ram disks with battery backups available recently.
>> These ram disks are relatively cheap and could add great performance for
>> write through without the fear of data loss.
>>
>> Any interest in adding support for this?
>> --
>> 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
>>
>
>
>
> --
> Roberto Spadim
> Spadim Technology / SPAEmpresarial
>
--
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
next prev parent reply other threads:[~2011-01-19 3:17 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 [this message]
2011-01-19 3:34 ` Cory Coager
2011-01-19 15:19 ` Roberto Spadim
2011-01-19 15:52 ` Cory Coager
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=AANLkTim3BJVbHdtByAni2ObUf0Qjece9jkd1_MSkT56P@mail.gmail.com \
--to=roberto@spadim.com.br \
--cc=ccoager@gmail.com \
--cc=linux-raid@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).