From: Hugh Dickins <hughd@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Julian Wollrath <julian.wollrath@stud.uni-goettingen.de>,
Julian Wollrath <jwollrath@web.de>,
Patrik Kullman <patrik.kullman@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, David Rientjes <rientjes@google.com>
Subject: Re: Major performance regressions in 3.7rc1/2
Date: Mon, 22 Oct 2012 21:20:55 -0700 (PDT) [thread overview]
Message-ID: <alpine.LNX.2.00.1210222059120.1136@eggly.anvils> (raw)
In-Reply-To: <20121022170452.cc8cc629.akpm@linux-foundation.org>
On Mon, 22 Oct 2012, Andrew Morton wrote:
> On Mon, 22 Oct 2012 21:45:02 +0200
> Julian Wollrath <julian.wollrath@stud.uni-goettingen.de> wrote:
>
> > Hello,
> >
> > seems like I found the other bad commit. Everything, which means
> > v3.7-rc*, works fine again with commit e6c509f85 (mm: use
> > clear_page_mlock() in page_remove_rmap()) and commit 957f822a0 (mm,
> > numa: reclaim from all nodes within reclaim distance) revoked.
>
> Thanks. Let's add some cc's. Can you please describe your workload
> and some estimate of the slowdown?
I'm currently assuming that my clear_page_mlock() commit is innocent
of this: it went in just two before David's numa reclaim commit, and
I don't see how mine could have any such marked effect: I'm thinking
it was just a bisection hiccup that implicated it.
Julian (or Patrik), what do you find if you revert the numa reclaim
commit but leave in the clear_page_mlock commit? Or vice versa.
Whereas David's numa reclaim distance commit does look suspicious to
me: as I read it (perhaps wrongly), zone_reclaim_mode would previously
have stayed 0 if all nodes were close or equidistant (e.g. CONFIG_NUMA=y
on a non-NUMA machine), but now it would be 1 in this case, invoking
zone_reclaim() more frequently than before.
Hugh
>
> Patrik has also seen this and his description is
>
> : I'm using an Asus Zenbook UX31E and have been installing all RCs in
> : hope of improving the Wireless and Touchpad functionality.
> : However, when trying 3.7 (rc1 and now rc2) I have major performance issues.
> :
> : Easiest way to reproduce is to launch and play a game like Nexuiz,
> : where the computer will lag, stutter and freeze until the machine is
> : unresponsive within a couple of minutes.
> : But an easy workload like browsing will also cause lags when switching
> : tabs or redrawing a web page after a tab switch.
> : Basically 3.7 is unusable for this machine.
--
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:[~2012-10-23 4:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGPN=9Qx1JAr6CGO-JfoR2ksTJG_CLLZY_oBA_TFMzA_OSfiFg@mail.gmail.com>
[not found] ` <20121022173315.7b0da762@ilfaris>
[not found] ` <20121022214502.0fde3adc@ilfaris>
2012-10-23 0:04 ` Andrew Morton
2012-10-23 4:20 ` Hugh Dickins [this message]
2012-10-23 9:04 ` Julian Wollrath
2012-10-23 10:52 ` Anca Emanuel
2012-10-23 22:42 ` David Rientjes
2012-10-23 23:15 ` Anca Emanuel
2012-10-24 1:55 ` [patch for-3.7] mm, numa: avoid setting zone_reclaim_mode unless a node is sufficiently distant David Rientjes
2012-10-24 8:38 ` Julian Wollrath
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=alpine.LNX.2.00.1210222059120.1136@eggly.anvils \
--to=hughd@google.com \
--cc=akpm@linux-foundation.org \
--cc=julian.wollrath@stud.uni-goettingen.de \
--cc=jwollrath@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=patrik.kullman@gmail.com \
--cc=rientjes@google.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