From: Chris Mason <chris.mason@oracle.com>
To: Miguel Sousa Filipe <miguel.filipe@gmail.com>
Cc: Kaspar Schleiser <kaspar@schleiser.de>, linux-btrfs@vger.kernel.org
Subject: Re: feature request: read/write priorities on multiple devices/raid1
Date: Thu, 25 Sep 2008 12:15:02 -0400 [thread overview]
Message-ID: <1222359302.7028.38.camel@think.oraclecorp.com> (raw)
In-Reply-To: <f058a9c30809250831r5479c4fcyac4deade9ddfda0e@mail.gmail.com>
On Thu, 2008-09-25 at 16:31 +0100, Miguel Sousa Filipe wrote:
> Hi all,
>
> On Thu, Sep 25, 2008 at 2:10 PM, Chris Mason <chris.mason@oracle.com> wrote:
> > On Thu, 2008-09-25 at 11:19 +0200, Kaspar Schleiser wrote:
> >> Hello everybody!
> >>
> >> This is my first post on the list, let me know if I'm not following any
> >> rules.
> >>
> >> What do you think about adding priorities for raid1 arrays?
> >>
> >> For example, always use /dev/ram0 (ramdisk) for reading/writing, but
> >> nonetheless write everything additionally on /dev/sda1. Restore to
> >> /dev/ram0 after mount if it is empty.
> >>
> >
> > I don't plan on adding support for non-persistent storage, but there
> > will be the idea of a fast frontend device that is basically a cache for
> > slower devices.
>
> Something like yet another caching/buffer layer between the buffer
> cache and the storage devices?
>
Not really a caching layer, more of a block allocation group that when
full migrates old blocks to a different block allocation group.
> I recall reading something similiar to that in a listing of new
> features of a recent revision of ZFS ?
>
Sorry, no idea.
-chris
next prev parent reply other threads:[~2008-09-25 16:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 9:19 feature request: read/write priorities on multiple devices/raid1 Kaspar Schleiser
2008-09-25 11:27 ` Jeff Schroeder
2008-09-25 13:10 ` Chris Mason
2008-09-25 15:31 ` Miguel Sousa Filipe
2008-09-25 15:49 ` Xavier Nicollet
2008-09-25 16:15 ` Chris Mason [this message]
2008-10-19 6:34 ` Chris Samuel
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=1222359302.7028.38.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=kaspar@schleiser.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=miguel.filipe@gmail.com \
/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