From: Michal Hocko <mhocko@kernel.org>
To: Thierry <reserv0@yahoo.com>
Cc: Alkis Georgopoulos <alkisg@gmail.com>,
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: Fri, 17 Aug 2018 11:29:23 +0200 [thread overview]
Message-ID: <20180817092923.GB709@dhcp22.suse.cz> (raw)
In-Reply-To: <328204943.8183321.1534496501208@mail.yahoo.com>
On Fri 17-08-18 09:01:41, Thierry wrote:
> Bug still present for 32 bits kernel in v4.18.1, and now, v4.1 (last
> working Linux kernel for 32 bits machines with 16Gb or more RAM) has
> gone unmaintained...
Have you tried to set highmem_is_dirtyable as suggested elsewhere?
I would like to stress out that 16GB with 32b kernels doesn't play
really nice. Even small changes (larger kernel memory footprint) can
lead to all sorts of problems. I would really recommend using 64b
kernels instead. There shouldn't be any real reason to stick with 32b
highmem based kernel for such a large beast. I strongly doubt the cpu
itself would be 32b only.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-08-17 9:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <328204943.8183321.1534496501208.ref@mail.yahoo.com>
2018-08-17 9:01 ` [Bug 196157] New: 100+ times slower disk writes on 4.x+/i386/16+RAM, compared to 3.x Thierry
2018-08-17 9:29 ` Michal Hocko [this message]
[not found] <1978465524.8206495.1534505385491.ref@mail.yahoo.com>
2018-08-17 11:29 ` Thierry
2018-08-17 14:46 ` Michal Hocko
[not found] <234273956.1792577.1524210929280.ref@mail.yahoo.com>
2018-04-20 7:55 ` Thierry
[not found] <bug-196157-27@https.bugzilla.kernel.org/>
2017-06-22 19:37 ` 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
2017-06-29 7:16 ` Michal Hocko
2017-06-29 8:02 ` Alkis Georgopoulos
2018-04-19 20:36 ` Andrew Morton
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=20180817092923.GB709@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alkisg@gmail.com \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=reserv0@yahoo.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).