From: Peter Zijlstra <peterz@infradead.org>
To: Mike Galbraith <efault@gmx.de>
Cc: LKML <linux-kernel@vger.kernel.org>, Andy Lutomirski <luto@kernel.org>
Subject: Re: 4.13..4.14 scheduling overhead regression (bisected - b956575bed91)
Date: Fri, 1 Jun 2018 15:20:55 +0200 [thread overview]
Message-ID: <20180601132055.GT12198@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1527857873.4674.11.camel@gmx.de>
On Fri, Jun 01, 2018 at 02:57:53PM +0200, Mike Galbraith wrote:
> b956575bed91ecfb136a8300742ecbbf451471ab is the first bad commit
> commit b956575bed91ecfb136a8300742ecbbf451471ab
> Author: Andy Lutomirski <luto@kernel.org>
> Date: Mon Oct 9 09:50:49 2017 -0700
>
> x86/mm: Flush more aggressively in lazy TLB mode
Oh boy... Maybe we should start looking at that optimization Andy
mentioned.
IIRC all page freeing does indeed go through tlb_remove_page(), it
shouldn't be too hard to make that work.
next prev parent reply other threads:[~2018-06-01 13:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 12:57 Mike Galbraith
2018-06-01 13:20 ` Peter Zijlstra [this message]
2018-06-01 15:09 ` Andy Lutomirski
2018-06-01 18:56 ` Rik van Riel
2018-06-04 7:25 ` Peter Zijlstra
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=20180601132055.GT12198@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@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
all inboxes | Powered by JetHome®