From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: for.poige+linux@gmail.com, linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>
Subject: Re: That greedy Linux VM cache
Date: Fri, 31 Jan 2014 11:57:55 -0500 [thread overview]
Message-ID: <52EBD613.3040902@gmail.com> (raw)
In-Reply-To: <CA+sTkh4p10P_BbxEx0vxS9uF0zA9G97K+4B_Q1Np55Ui83LVDQ@mail.gmail.com>
On 01/31/2014 09:47 AM, Igor Podlesny wrote:
> On 31 January 2014 00:58, Igor Podlesny <for.poige+linux@gmail.com> wrote:
> [...]
>> While I'm thinking about moving system back to XFS...
>
> Well, it helped just a bit. The whole picture remains, so it's not
> Btrfs' issue, but seemingly Linux VM's one. The problem can be briefly
> described as "if allowed to swap (swappiness != 0), VM would rather
> start swapping, than reduce cache size which holds ~ 25 % of RAM".
> Even more briefly it's stated in the Subject.
>
> From user's point of view, it looks like the system is being
> heavily swapped (and can be easily misinterpreted as it), but actually
> the most disk activity is permanent _reading_ from filesystem, and not
> accessing swap device.
>
> Should I fill in a bug report in kernel's bugzilla, or just upgrade
> the notebook? )
>
If I remember correctly, there is a sysctl for configuring how
aggressively the system tries to retain the VFS cache, changing the
value there might improve things for you.
next prev parent reply other threads:[~2014-01-31 16:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 16:58 That greedy Linux VM cache Igor Podlesny
2014-01-30 17:06 ` David Lang
2014-01-31 14:47 ` Igor Podlesny
2014-01-31 16:57 ` Austin S. Hemmelgarn [this message]
2014-01-31 17:08 ` Igor Podlesny
2014-01-31 18:25 ` Henrique de Moraes Holschuh
2014-02-03 10:55 ` Michal Hocko
-- strict thread matches above, loose matches on Subject: below --
2014-02-08 19:42 Igor Podlesny
2014-02-10 13:33 ` Michal Hocko
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=52EBD613.3040902@gmail.com \
--to=ahferroin7@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=for.poige+linux@gmail.com \
--cc=linux-kernel@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