From: Thierry <reserv0@yahoo.com>
To: Alkis Georgopoulos <alkisg@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Michal Hocko <mhocko@kernel.org>,
linux-mm@kvack.org, bugzilla-daemon@bugzilla.kernel.org,
Mel Gorman <mgorman@techsingularity.net>,
Johannes Weiner <hannes@cmpxchg.org>,
reserv0@yahoo.com
Subject: Re: [Bug 196157] New: 100+ times slower disk writes on 4.x+/i386/16+RAM, compared to 3.x
Date: Fri, 20 Apr 2018 07:55:29 +0000 (UTC) [thread overview]
Message-ID: <234273956.1792577.1524210929280@mail.yahoo.com> (raw)
In-Reply-To: 234273956.1792577.1524210929280.ref@mail.yahoo.com
On Thu, 4/19/18, Andrew Morton <akpm@linux-foundation.org> wrote:
> (switched to email. Please respond via emailed reply-to-all, not via the
> bugzilla web interface).
>
> https://bugzilla.kernel.org/show_bug.cgi?id=196157
>
> People are still hurting from this. It does seem a pretty major
> regression for highmem machines.
>
> I'm surprised that we aren't hearing about this from distros. Maybe it
> only affects a subset of highmem machines?
Supposition: it would only affect distros with a given glibc version (my
affected machines run glibc v2.13) ?
Please, also take note that I encountered this bug on the 64 bits flavor of the
same distro (Rosa 2012), on 64 bits capable machines, with Linux v4.2+ and
until Linux v4.8.4 was released (and another interesting fact is that another
64 bits distro one the same machines was not affected at all by that bug,
which would reinforce my suspicion about a glibc-triggered and
glibc-version-dependent bug).
> Anyway, can we please take another look at it? Seems that we messed up
> highmem dirty pagecache handling in the 4.2 timeframe.
Oh, yes, please, do have a look ! :-D
In the mean time, could you guys also consider extending the lifetime of the
v4.1 kernel until this ***showstopper*** bug is resolved in the mainline kernel
version ?
Many (many, many, many) thanks in advance !
next parent reply other threads:[~2018-04-20 7:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <234273956.1792577.1524210929280.ref@mail.yahoo.com>
2018-04-20 7:55 ` Thierry [this message]
[not found] <1978465524.8206495.1534505385491.ref@mail.yahoo.com>
2018-08-17 11:29 ` [Bug 196157] New: 100+ times slower disk writes on 4.x+/i386/16+RAM, compared to 3.x Thierry
2018-08-17 14:46 ` Michal Hocko
[not found] <328204943.8183321.1534496501208.ref@mail.yahoo.com>
2018-08-17 9:01 ` Thierry
2018-08-17 9:29 ` Michal Hocko
[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=234273956.1792577.1524210929280@mail.yahoo.com \
--to=reserv0@yahoo.com \
--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=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).