[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181023122435.GB20085@bombadil.infradead.org>
Date: Tue, 23 Oct 2018 05:24:35 -0700
From: Matthew Wilcox <willy@...radead.org>
To: Souptick Joarder <jrdr.linux@...il.com>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>,
Russell King - ARM Linux <linux@...linux.org.uk>,
robin@...tonic.nl, stefanr@...6.in-berlin.de, hjc@...k-chips.com,
Heiko Stuebner <heiko@...ech.de>, airlied@...ux.ie,
robin.murphy@....com, iamjoonsoo.kim@....com,
Andrew Morton <akpm@...ux-foundation.org>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Kees Cook <keescook@...omium.org>, treding@...dia.com,
Michal Hocko <mhocko@...e.com>,
Dan Williams <dan.j.williams@...el.com>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Mark Rutland <mark.rutland@....com>, aryabinin@...tuozzo.com,
Dmitry Vyukov <dvyukov@...gle.com>,
Kate Stewart <kstewart@...uxfoundation.org>, tchibo@...gle.com,
riel@...hat.com, Minchan Kim <minchan@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
"Huang, Ying" <ying.huang@...el.com>, ak@...ux.intel.com,
rppt@...ux.vnet.ibm.com, linux@...inikbrodowski.net,
Arnd Bergmann <arnd@...db.de>, cpandya@...eaurora.org,
hannes@...xchg.org, Joe Perches <joe@...ches.com>,
mcgrof@...nel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org,
linux1394-devel@...ts.sourceforge.net,
dri-devel@...ts.freedesktop.org,
linux-rockchip@...ts.infradead.org, Linux-MM <linux-mm@...ck.org>
Subject: Re: [PATCH v2] mm: Introduce new function vm_insert_kmem_page
On Tue, Oct 23, 2018 at 05:44:32PM +0530, Souptick Joarder wrote:
> On Sat, Oct 6, 2018 at 4:19 PM Miguel Ojeda
> <miguel.ojeda.sandonis@...il.com> wrote:
> >
> > On Sat, Oct 6, 2018 at 7:11 AM Souptick Joarder <jrdr.linux@...il.com> wrote:
> > >
> > > On Fri, Oct 5, 2018 at 11:39 PM Miguel Ojeda
> > > <miguel.ojeda.sandonis@...il.com> wrote:
> > > > They are not supposed to be "steps". You did it with 70+ commits (!!)
> > > > over the course of several months. Why a tree wasn't created, stuff
> > > > developed there, and when done, submitted it for review?
> > >
> > > Because we already have a plan for entire vm_fault_t migration and
> > > the * instruction * was to send one patch per driver.
> >
> > The instruction?
>
> Sorry for the delayed response.
> Instruction from Matthew Wilcox who is supervising the entire vm_fault_t
> migration work :-)
Hang on. That was for the initial vm_fault_t conversion in which each
step was clearly an improvement. What you're looking at now is far
from that.
Powered by blists - more mailing lists