linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Janek Kozicki <janek_listy@wp.pl>
To: Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: raid1 on HDD + RAM ?
Date: Tue, 30 Sep 2008 21:36:17 +0200	[thread overview]
Message-ID: <20080930213617.0da1f315@szpak> (raw)
In-Reply-To: <20080930182129.GA28669@cthulhu.home.robinhill.me.uk>

Robin Hill said:     (by the date of Tue, 30 Sep 2008 19:21:29 +0100)

> I don't see why it wouldn't be possible.  I would think you'd get the
> same performance leaving the RAM for caching though - that way anything
> you _are_ actually reading/writing will be cached and the RAM is still
> available for applications if needed.


yes, I know. But in my case this won't work. This data which I want
quickly is seldom accessed therefore it will not be cached.


-- 
Janek Kozicki                                                         |

      reply	other threads:[~2008-09-30 19:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-30 15:49 raid1 on HDD + RAM ? Janek Kozicki
2008-09-30 17:09 ` David Greaves
2008-09-30 19:21   ` Janek Kozicki
2008-09-30 20:43     ` David Greaves
2008-09-30 18:21 ` Robin Hill
2008-09-30 19:36   ` Janek Kozicki [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=20080930213617.0da1f315@szpak \
    --to=janek_listy@wp.pl \
    --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).