linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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:37:59 -0200	[thread overview]
Message-ID: <AANLkTimOPNY+0Yq18c1x+ON1YKFgHmep0GHCgAnt9pyb@mail.gmail.com> (raw)
In-Reply-To: <20110119172907.GA1342@erebus.underworld.local>

please check my email =)
let´s end this email?

2011/1/19 Cory Coager <ccoager@gmail.com>:
> On Wed, Jan 19, 2011 at 03:15:40PM -0200, Roberto Spadim wrote:
>> hummm....
>> thinking again.....
>>
>> what?s the today raid1 problem?
>> it?s based on minimal disk size
>> for example...
>> /dev/sda 1gb
>> /dev/sdb 1tb
>> we can have a 1gb raid only
>>
>> what you want is:
>> 1tb raid0
>> with a automatic /dev/sda to /dev/sdb write
>>
>>
>> could we call this raid0-cache?
>> i think we could implement it in raid....
>>
>> check this fuse (filesystem) implementation: http://www.furquim.org/chironfs/
>> it?s based on filesystem (ok it?s a raid1, not a cache like, but?s
>> limited to max filesystem size, not the minimal filesystem size... ok
>> it?s not secure to use it since small filesystem don?t have all
>> information, but?s nice)
>>
>> anyone want to make raid0-cache implementation?
>
> I have two comments on this.
>
> I don't think the cache device should be the same size as your
> disk storage.  It should be a small cache size similar to
> hardware RAID.
>
> Also, we'd need a way to flush the data from the cache device
> on bootup.
> --
> 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

      reply	other threads:[~2011-01-19 17:37 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
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 [this message]

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=AANLkTimOPNY+0Yq18c1x+ON1YKFgHmep0GHCgAnt9pyb@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).