From: Alkis Georgopoulos <alkisg@gmail.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, bugzilla-daemon@bugzilla.kernel.org,
Mel Gorman <mgorman@techsingularity.net>,
Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [Bug 196157] New: 100+ times slower disk writes on 4.x+/i386/16+RAM, compared to 3.x
Date: Thu, 29 Jun 2017 09:14:55 +0300 [thread overview]
Message-ID: <5eff5b8f-51ab-9749-0da5-88c270f0df92@gmail.com> (raw)
In-Reply-To: <20170626091254.GG11534@dhcp22.suse.cz>
I've been working on a system with highmem_is_dirtyable=1 for a couple
of hours.
While the disk benchmark showed no performance hit on intense disk
activity, there are other serious problems that make this workaround
unusable.
I.e. when there's intense disk activity, the mouse cursor moves with
extreme lag, like 1-2 fps. Switching with alt+tab from e.g. thunderbird
to pidgin needs 10 seconds. kswapd hits 100% cpu usage. Etc etc, the
system becomes unusable until the disk activity settles down.
I was testing via SSH so I hadn't noticed the extreme lag.
All those symptoms go away when resetting highmem_is_dirtyable=0.
So currently 32bit installations with 16 GB RAM have no option but to
remove the extra RAM...
About ab8fabd46f81 ("mm: exclude reserved pages from dirtyable memory"),
would it make sense for me to compile a kernel and test if everything
works fine without it? I.e. if we see that this caused all those
regressions, would it be revisited?
And an unrelated idea, is there any way to tell linux to use a limited
amount of RAM for page cache, e.g. only 1 GB?
Kind regards,
Alkis Georgopoulos
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-06-29 6:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-196157-27@https.bugzilla.kernel.org/>
2017-06-22 19:37 ` [Bug 196157] New: 100+ times slower disk writes on 4.x+/i386/16+RAM, compared to 3.x Andrew Morton
2017-06-22 20:58 ` Alkis Georgopoulos
2017-06-23 7:13 ` Michal Hocko
2017-06-23 7:44 ` Alkis Georgopoulos
2017-06-23 11:38 ` Michal Hocko
2017-06-26 5:28 ` Alkis Georgopoulos
2017-06-26 5:46 ` Michal Hocko
2017-06-26 7:02 ` Alkis Georgopoulos
2017-06-26 9:12 ` Michal Hocko
2017-06-29 6:14 ` Alkis Georgopoulos [this message]
2017-06-29 7:16 ` Michal Hocko
2017-06-29 8:02 ` Alkis Georgopoulos
2018-04-19 20:36 ` Andrew Morton
[not found] <234273956.1792577.1524210929280.ref@mail.yahoo.com>
2018-04-20 7:55 ` Thierry
[not found] <328204943.8183321.1534496501208.ref@mail.yahoo.com>
2018-08-17 9:01 ` Thierry
2018-08-17 9:29 ` Michal Hocko
[not found] <1978465524.8206495.1534505385491.ref@mail.yahoo.com>
2018-08-17 11:29 ` Thierry
2018-08-17 14:46 ` 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=5eff5b8f-51ab-9749-0da5-88c270f0df92@gmail.com \
--to=alkisg@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@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).