linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Alkis Georgopoulos <alkisg@gmail.com>
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: Thu, 19 Apr 2018 13:36:34 -0700	[thread overview]
Message-ID: <20180419133634.77035d22766e017cd876e170@linux-foundation.org> (raw)
In-Reply-To: <c84a30f7-0524-5a30-e825-7e73d0cb06e2@gmail.com>


(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?

Anyway, can we please take another look at it?  Seems that we messed up
highmem dirty pagecache handling in the 4.2 timeframe.

Thanks.

  reply	other threads:[~2018-04-19 20:36 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
2017-06-29  7:16                   ` Michal Hocko
2017-06-29  8:02                     ` Alkis Georgopoulos
2018-04-19 20:36                       ` Andrew Morton [this message]
     [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=20180419133634.77035d22766e017cd876e170@linux-foundation.org \
    --to=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 \
    --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).