From: Andrew Morton <akpm@linux-foundation.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Laurent Dufour <ldufour@linux.vnet.ibm.com>,
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: Mon, 25 Sep 2017 16:34:43 -0700 [thread overview]
Message-ID: <20170925163443.260d6092160ec704e2b04653@linux-foundation.org> (raw)
In-Reply-To: <CAADnVQLmSbLHwj9m33kpzAidJPvq3cbdnXjaew6oTLqHWrBbZQ@mail.gmail.com>
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'll be taking a close look at it all over the next couple of weeks.
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.
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(?). 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.
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Laurent Dufour <ldufour@linux.vnet.ibm.com>,
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: Mon, 25 Sep 2017 16:34:43 -0700 [thread overview]
Message-ID: <20170925163443.260d6092160ec704e2b04653@linux-foundation.org> (raw)
In-Reply-To: <CAADnVQLmSbLHwj9m33kpzAidJPvq3cbdnXjaew6oTLqHWrBbZQ@mail.gmail.com>
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'll be taking a close look at it all over the next couple of weeks.
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.
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(?). 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.
--
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-25 23:34 UTC|newest]
Thread overview: 30+ 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 16:27 ` Alexei Starovoitov
2017-09-25 23:34 ` Andrew Morton [this message]
2017-09-25 23:34 ` Andrew Morton
2017-09-28 12:17 ` Laurent Dufour
2017-09-28 12:17 ` Laurent Dufour
2017-09-28 12:29 ` Laurent Dufour
2017-09-28 12:29 ` Laurent Dufour
2017-09-28 20:38 ` Andrew Morton
2017-09-28 20:38 ` Andrew Morton
2017-09-29 15:27 ` Laurent Dufour
2017-09-29 15:27 ` Laurent Dufour
2017-10-03 1:27 ` Michael Ellerman
2017-10-03 1:27 ` Michael Ellerman
2017-10-03 8:03 ` Laurent Dufour
2017-10-03 8:03 ` Laurent Dufour
2017-09-26 8:30 ` Laurent Dufour
2017-09-26 8:30 ` Laurent Dufour
2017-10-04 6:50 ` Laurent Dufour
2017-10-04 6:50 ` Laurent Dufour
2017-10-05 23:32 ` Alexei Starovoitov
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-08 18:06 ` Laurent Dufour
2017-09-18 7:15 ` Laurent Dufour
2017-09-18 7:15 ` Laurent Dufour
2017-09-08 17:32 Laurent Dufour
2017-09-08 17:32 ` Laurent Dufour
2017-09-08 17:44 ` 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=20170925163443.260d6092160ec704e2b04653@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ak@linux.intel.com \
--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=ldufour@linux.vnet.ibm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.