From: Roman Mamedov <rm@romanrm.net>
To: Robert Kierski <rkierski@cray.com>
Cc: Adam Goryachev <adam@websitemanagers.com.au>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: stripe_cache_active always 0
Date: Thu, 7 Jan 2016 22:52:43 +0500 [thread overview]
Message-ID: <20160107225243.74f5549b@natsu> (raw)
In-Reply-To: <F7761B9B1D11B64BBB666019E9378117FE848B@CFWEX01.americas.cray.com>
[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]
On Thu, 7 Jan 2016 16:34:36 +0000
Robert Kierski <rkierski@cray.com> wrote:
> As far as adjusting stripe_cache_size... The stripe cache is dynamically allocated. It won't save any RAM by decreasing stripe_cache_size.
Since when?
# echo 512 > /sys/devices/virtual/block/md0/md/stripe_cache_size
# free
total used free shared buffers cached
Mem: 16159912 15672696 487216 12588 52 14484708
-/+ buffers/cache: 1187936 14971976
Swap: 0 0 0
# echo 32768 > /sys/devices/virtual/block/md0/md/stripe_cache_size
# free
total used free shared buffers cached
Mem: 16159912 15957880 202032 12588 52 14214952
-/+ buffers/cache: 1742876 14417036
Swap: 0 0 0
You can see that's not the case (on kernel 4.3.3 with four-member RAID5);
And it's quite easy to rapidly hit OOM issues on high-member-count arrays by
setting stripe_cache_size to larger values (not realizing that this is *in
pages* not kilobytes or sectors, and *per disk*).
As for the original question, try checking stripe_cache_active e.g. once
per second during heavy write load to the filesystem.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-01-07 17:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 3:09 stripe_cache_active always 0 Adam Goryachev
2016-01-07 16:34 ` Robert Kierski
2016-01-07 17:52 ` Roman Mamedov [this message]
2016-01-07 17:53 ` {Possible Spam} " Benjamin ESTRABAUD
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=20160107225243.74f5549b@natsu \
--to=rm@romanrm.net \
--cc=adam@websitemanagers.com.au \
--cc=linux-raid@vger.kernel.org \
--cc=rkierski@cray.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;
as well as URLs for NNTP newsgroup(s).