From: Laurent Dufour <ldufour@linux.vnet.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Paul McKenney <paulmck@linux.vnet.ibm.com>,
Peter Zijlstra <peterz@infradead.org>,
kirill@shutemov.name, Andi Kleen <ak@linux.intel.com>,
Michal Hocko <mhocko@kernel.org>,
dave@stgolabs.net, Jan Kara <jack@suse.cz>,
Matthew Wilcox <willy@infradead.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Paul Mackerras <paulus@samba.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Will Deacon <will.deacon@arm.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
haren@linux.vnet.ibm.com,
Anshuman Khandual <khandual@linux.vnet.ibm.com>,
npiggin@gmail.com, bsingharora@gmail.com,
Tim Chen <tim.c.chen@linux.intel.com>,
linuxppc-dev@lists.ozlabs.org, "x86@kernel.org" <x86@kernel.org>
Subject: Re: [PATCH v3 00/20] Speculative page faults
Date: Thu, 28 Sep 2017 14:17:22 +0200 [thread overview]
Message-ID: <d6ceae3b-09c0-0642-ff56-c31d044e805e@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170925163443.260d6092160ec704e2b04653@linux-foundation.org>
Hi,
On 26/09/2017 01:34, Andrew Morton wrote:
> On Mon, 25 Sep 2017 09:27:43 -0700 Alexei Starovoitov <alexei.starovoitov@gmail.com> wrote:
>
>> On Mon, Sep 18, 2017 at 12:15 AM, Laurent Dufour
>> <ldufour@linux.vnet.ibm.com> wrote:
>>> Despite the unprovable lockdep warning raised by Sergey, I didn't get any
>>> feedback on this series.
>>>
>>> Is there a chance to get it moved upstream ?
>>
>> what is the status ?
>> We're eagerly looking forward for this set to land,
>> since we have several use cases for tracing that
>> will build on top of this set as discussed at Plumbers.
>
> There has been sadly little review and testing so far :(
I do agree and I could just encourage people to do so :/
> I'll be taking a close look at it all over the next couple of weeks.
Thanks Andrew for giving it a close look.
> One terribly important thing (especially for a patchset this large and
> intrusive) is the rationale for merging it: the justification, usually
> in the form of end-user benefit.
The benefit is only for multi-threaded processes. But even on *small*
systems with 16 CPUs, there is a real benefit.
>
> Laurent's [0/n] provides some nice-looking performance benefits for
> workloads which are chosen to show performance benefits(!) but, alas,
> no quantitative testing results for workloads which we may suspect will
> be harmed by the changes(?).
I did test with kernbench, involving gcc/ld which are not
multi-threaded, AFAIK, and I didn't see any impact.
But if you know additional test I should give a try, please advise.
Regarding ebizzy, it was designed to simulate web server's activity, so
I guess there will be improvements when running real web servers.
> Even things as simple as impact upon
> single-threaded pagefault-intensive workloads and its effect upon
> CONFIG_SMP=n .text size?
>
> If you have additional usecases then please, spell them out for us in
> full detail so we can better understand the benefits which this
> patchset provides.
The other use-case I'm aware of is on memory database, where performance
improvements is really significant, as I mentioned in the header of my
series.
Cheers,
Laurent.
--
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:[~2017-09-28 12:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 16:27 [PATCH v3 00/20] Speculative page faults Alexei Starovoitov
2017-09-25 23:34 ` Andrew Morton
2017-09-28 12:17 ` Laurent Dufour [this message]
2017-09-28 12:29 ` Laurent Dufour
2017-09-28 20:38 ` Andrew Morton
2017-09-29 15:27 ` Laurent Dufour
2017-10-03 1:27 ` Michael Ellerman
2017-10-03 8:03 ` Laurent Dufour
2017-09-26 8:30 ` Laurent Dufour
2017-10-04 6:50 ` Laurent Dufour
2017-10-05 23:32 ` Alexei Starovoitov
-- strict thread matches above, loose matches on Subject: below --
2017-09-08 18:06 Laurent Dufour
2017-09-18 7:15 ` Laurent Dufour
2017-09-08 17:32 Laurent Dufour
2017-09-08 17:44 ` Laurent Dufour
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=d6ceae3b-09c0-0642-ff56-c31d044e805e@linux.vnet.ibm.com \
--to=ldufour@linux.vnet.ibm.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=alexei.starovoitov@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=bsingharora@gmail.com \
--cc=dave@stgolabs.net \
--cc=haren@linux.vnet.ibm.com \
--cc=hpa@zytor.com \
--cc=jack@suse.cz \
--cc=khandual@linux.vnet.ibm.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mhocko@kernel.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.com \
--cc=will.deacon@arm.com \
--cc=willy@infradead.org \
--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).