From: rabbit@rabbit.us (Peter Rabbitson)
To: linux-raid@vger.kernel.org
Subject: Re: swap on raid
Date: Thu, 1 Mar 2007 18:34:20 -0500 [thread overview]
Message-ID: <20070301233420.GA12963@rabbit.us> (raw)
In-Reply-To: <45E75CBC.2050003@sauce.co.nz>
> The fact that you mention you are using partitions on disks that
> possibly have other partions doing other things, means raw performance
> will be compromised anyway.
>
> Regards,
>
> Richard
You know I never thought about it, but you are absolutely right. The
times at which my memory usage peaks coincide with high disk activity
(mostly reads). In this light it actually might be better to keep the
swap in a file on my raid10 (-p n3) which occupies most of these 4
drives, and hope that the md code will be able to distribute the io
across idle drives. Does this sound about right?
next prev parent reply other threads:[~2007-03-01 23:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 22:27 swap on raid Peter Rabbitson
2007-03-01 22:30 ` Justin Piszcz
2007-03-01 23:07 ` Richard Scobie
2007-03-01 23:34 ` Peter Rabbitson [this message]
2007-03-02 4:45 ` Mark Hahn
2007-03-01 23:24 ` Bill Davidsen
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=20070301233420.GA12963@rabbit.us \
--to=rabbit@rabbit.us \
--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).