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 15:09:04 -0200 [thread overview]
Message-ID: <AANLkTinG9LeZOevLM1WRT-H_fgk5wTY8tmGkadrzS0pH@mail.gmail.com> (raw)
In-Reply-To: <20110119170252.GA891@erebus.underworld.local>
i think we could make it
but not a raid feature
a linux feature
for example
we could get ramdisk, nbd (network block device), ssd, hd, scsi, raid
and select what is first cache, and what is real value
after this device is created we could use it with raid...
but.... the problem persist
if we lost energy, we can´t confirm that ram memory is sync to disk,
just if we don´t use memory cache... in other words we will work with
the best cache disk speed)
since ram can get 32GB on big home computer
and ssd can get 1terabyte on big home computer
and hdd can get more than 1terabyte on big home computer
we just need time to sync 32GB from memory to ssd
what´s the ssd speed? 300mb/s? we need 106,6666666666667 seconds to
sync memory to ssd, can you buy a ups with 107 seconds of life with a
serial cable (usb maybe) that inform that we are without energy?
2011/1/19 Cory Coager <ccoager@gmail.com>:
> On Wed, Jan 19, 2011 at 02:44:31PM -0200, Roberto Spadim wrote:
>> yes, a jornaling but using ssd first and sata after
>> it?s not raid feature...
>> it?s per disk filesystem feature...
>> we could implement jornaling in raid too...
>> but?s more inteligent (easy) at application level (filesystem)
>> you could write first at network (if it?s faster than sata) and after
>> at sata (if it?s slower than network)
>>
>> it?s not a raid feature... it?s a per device feature got it?
>> maybe a device (not raid..) for a cache division on devices
>> for example
>>
>>
>> /dev/sda (sata 1terabyte 100mb/s)
>> /dev/sdb (ssd 1gigabyte 1000mb/s)
>>
>> /dev/cache_a (a mix of sata and ssd with sata size 1terabyte, and
>> mixed speed (memory, ssd, sata))
>>
>> cache_a device should know that
>> early reads/write should be writen to sdb
>> time in time it should sync at sda
>>
>> the same happens with memory (ram memory) but it?s volatille (diferent
>> than ssd that?s not volatille)
>>
>> /dev/sdb should be sync
>> /dev/sda should be async (since /dev/sdb make it safe to use async)
>>
>>
>> that?s you intention? i don?t know if linux have it, anyone know?
> I would use a physical ramdisk over a ssd but thats besides the point.
> They are still disk drives to the OS.
>
> Yes, I guess it would be similar to journaling but done in RAID
> itself. I don't believe it exists yet, thats why I'm asking if
> we could add 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
--
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 17:09 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
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 [this message]
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=AANLkTinG9LeZOevLM1WRT-H_fgk5wTY8tmGkadrzS0pH@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).