From: Peter Zijlstra <peterz@infradead.org>
To: Waiman Long <longman@redhat.com>
Cc: Ingo Molnar <mingo@redhat.com>, Will Deacon <will.deacon@arm.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, x86@kernel.org,
Davidlohr Bueso <dave@stgolabs.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
Tim Chen <tim.c.chen@linux.intel.com>,
huang ying <huang.ying.caritas@gmail.com>
Subject: Re: [PATCH-tip 0/2] locking/rwsem: Rwsem rearchitecture part 2 follow-up patches
Date: Tue, 16 Apr 2019 15:10:47 +0200 [thread overview]
Message-ID: <20190416131047.GW11158@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20190415205829.32707-1-longman@redhat.com>
On Mon, Apr 15, 2019 at 04:58:27PM -0400, Waiman Long wrote:
> This series contain 2 follow-up patches to alleviate the performance
> regression found in the page_fault1 test of the will-it-scale benchmark.
> This does not recover all the lost performance, but reclaim a sizeable
> portion of it.
>
> The regression was found on an Intel system. I have run the test on
> an AMD system. The regression wasn't seen there. There are only minor
> variations in performance. Perhaps the page fault path is quite different
> between Intel and AMD systems.
Can you please just fold this back into the appropriate patches? Trying
to review all the back and forth is painful.
next prev parent reply other threads:[~2019-04-16 13:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 20:58 [PATCH-tip 0/2] locking/rwsem: Rwsem rearchitecture part 2 follow-up patches Waiman Long
2019-04-15 20:58 ` [PATCH-tip 1/2] locking/rwsem: Clarify usage of owner's nonspinaable bit Waiman Long
2019-04-15 20:58 ` [PATCH-tip 2/2] locking/rwsem: Adaptive disabling of reader optimistic spinning Waiman Long
2019-04-16 13:10 ` Peter Zijlstra [this message]
2019-04-16 13:18 ` [PATCH-tip 0/2] locking/rwsem: Rwsem rearchitecture part 2 follow-up patches Waiman Long
2019-04-16 14:17 ` Peter Zijlstra
2019-04-16 17:03 ` Waiman Long
2019-04-16 17:37 ` Peter Zijlstra
2019-04-16 19:49 ` Waiman Long
2019-04-17 5:57 ` Ingo Molnar
2019-04-17 20:30 ` Waiman Long
2019-04-18 8:02 ` Ingo Molnar
2019-04-18 12:42 ` Waiman Long
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=20190416131047.GW11158@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=dave@stgolabs.net \
--cc=huang.ying.caritas@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.com \
--cc=torvalds@linux-foundation.org \
--cc=will.deacon@arm.com \
--cc=x86@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).