From: Brad Campbell <brad@wasp.net.au>
To: RAID Linux <linux-raid@vger.kernel.org>
Subject: Re: Silly stripe cache values
Date: Sat, 25 Mar 2006 15:34:38 +0400 [thread overview]
Message-ID: <44252ACE.9020706@wasp.net.au> (raw)
In-Reply-To: <442528D7.1050302@wasp.net.au>
Brad Campbell wrote:
> G'day all,
>
> I have a box here.. it has a 2Ghz processor and 1.5GB of ram. It runs
> the entire OS over NFS and it's sole purpose in life is to run 15 SATA
> drives in a Raid-6 with ext3 on it, and share that over NFS. Most of
> that ram is sitting completely idle and thus I thought a logical thing
> to do would be to stuff as much of it as possible into the MD subsystem
> to help it cache..
>
> Are there any limits to the values living in /sys/block/md* and what
> might be the tradeoffs (if any) to using what would normally be thought
> stupid amounts of ram for these knobs ?
>
> This box does not get written to often, it's just a media streamer
> mostly.. but if I am writing to it then it chokes just providing a 1Mb
> stream over the network currently. (It's on a 2.6.15-git11 kernel
> currently but I'm just upgrading to 2.6.16 now)
Scratch that.. the limit appears to be 32768 and that works fine..
Google search results increase in accuracy proportionally with the elapsed time of a list posting
with the question.. :\
Brad
--
"Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so." -- Douglas Adams
next prev parent reply other threads:[~2006-03-25 11:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-25 11:26 Silly stripe cache values Brad Campbell
2006-03-25 11:34 ` Brad Campbell [this message]
2006-03-25 12:47 ` [PATCH] Add stripe cache entries to raid6 sysfs Brad Campbell
2006-03-30 5:10 ` Neil Brown
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=44252ACE.9020706@wasp.net.au \
--to=brad@wasp.net.au \
--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).