From: Tim Chen <tim.c.chen@linux.intel.com>
To: Waiman Long <longman@redhat.com>,
"Wang, Kemi" <kemi.wang@intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
"vbabka@suse.cz" <vbabka@suse.cz>,
Davidlohr Bueso <dave@stgolabs.net>
Cc: "yang.shi@linux.alibaba.com" <yang.shi@linux.alibaba.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Matthew Wilcox <willy@infradead.org>,
"mhocko@kernel.org" <mhocko@kernel.org>,
Colin King <colin.king@canonical.com>,
Andrew Morton <akpm@linux-foundation.org>,
"ldufour@linux.vnet.ibm.com" <ldufour@linux.vnet.ibm.com>,
"lkp@01.org" <lkp@01.org>,
"kirill.shutemov@linux.intel.com"
<kirill.shutemov@linux.intel.com>
Subject: Re: [LKP] [mm] 9bc8039e71: will-it-scale.per_thread_ops -64.1% regression
Date: Wed, 30 Jan 2019 16:06:36 -0800 [thread overview]
Message-ID: <907779d2-09a8-47fb-4d77-c907cd716b3c@linux.intel.com> (raw)
In-Reply-To: <9a6fdc15-4ce1-9c55-d660-a9825b9ae104@redhat.com>
On 12/27/18 6:55 PM, Waiman Long wrote:
> On 12/27/2018 08:31 PM, Wang, Kemi wrote:
>> Hi, Waiman
>> Did you post that patch? Let's see if it helps.
>
> I did post the patch a while ago. I will need to rebase it to a new
> baseline. Will do that in a week or 2.
>
> -Longman
>
Waiman,
In a large scale OLTP benchmark, we are also seeing a 1% loss in performance
from patch 9bc8039e71. We'll be interested to try out your patch to
restore some optimistic spinning on reader held sem.
Thanks.
Tim
next prev parent reply other threads:[~2019-01-31 0:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 5:08 [LKP] [mm] 9bc8039e71: will-it-scale.per_thread_ops -64.1% regression kernel test robot
2018-11-05 17:50 ` Linus Torvalds
2018-11-05 18:28 ` Yang Shi
2018-11-05 18:35 ` Linus Torvalds
2018-11-05 20:17 ` Yang Shi
2018-11-05 20:09 ` Vlastimil Babka
2018-11-05 22:14 ` Linus Torvalds
2018-11-05 22:40 ` Waiman Long
2018-12-28 1:31 ` Wang, Kemi
2018-12-28 2:55 ` Waiman Long
2018-12-28 2:55 ` kemi
2019-01-31 0:06 ` Tim Chen [this message]
2019-01-31 2:54 ` 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=907779d2-09a8-47fb-4d77-c907cd716b3c@linux.intel.com \
--to=tim.c.chen@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=colin.king@canonical.com \
--cc=dave@stgolabs.net \
--cc=kemi.wang@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=ldufour@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=longman@redhat.com \
--cc=mhocko@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
--cc=yang.shi@linux.alibaba.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