All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xavier Nicollet <nicollet@jeru.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: feature request: read/write priorities on multiple devices/raid1
Date: Thu, 25 Sep 2008 17:49:22 +0200	[thread overview]
Message-ID: <20080925154922.GL27002@jeru.org> (raw)
In-Reply-To: <f058a9c30809250831r5479c4fcyac4deade9ddfda0e@mail.gmail.com>

Le 25 septembre 2008 =E0 16:31, Miguel Sousa Filipe a =E9crit:
> On Thu, Sep 25, 2008 at 2:10 PM, Chris Mason <chris.mason@oracle.com>=
 wrote:
> > I don't plan on adding support for non-persistent storage, but ther=
e
> > will be the idea of a fast frontend device that is basically a cach=
e for
> > slower devices.
>=20
> Something like yet another caching/buffer layer between the buffer
> cache and the storage devices?
>=20
> I recall reading something similiar to that in a listing of new
> features of a recent revision of ZFS ?

Reminds me WAFL from netapp.

http://media.netapp.com/documents/wp_3002.pdf

Transactions are written to NVRAM, then flushed every 10 seconds.
If some files are created then imediately deleted, it won't even touch
the disk.

As the server "knows" the underlining RAID structure, it is able to
choose how to flush the data for maximum disk throughput.

I am not a specialist, but this document is worth reading IMHO.

--=20
Xavier Nicollet
http://nicollet.jeru.org/
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
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:[~2008-09-25 15:49 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 [this message]
2008-09-25 16:15     ` Chris Mason
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=20080925154922.GL27002@jeru.org \
    --to=nicollet@jeru.org \
    --cc=linux-btrfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.