[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190313180128.GV19891@mellanox.com>
Date: Wed, 13 Mar 2019 18:01:33 +0000
From: Jason Gunthorpe <jgg@...lanox.com>
To: Andrew Morton <akpm@...ux-foundation.org>
CC: Jerome Glisse <jglisse@...hat.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Felix Kuehling <Felix.Kuehling@....com>,
Christian König <christian.koenig@....com>,
Ralph Campbell <rcampbell@...dia.com>,
John Hubbard <jhubbard@...dia.com>,
Dan Williams <dan.j.williams@...el.com>
Subject: Re: [PATCH 00/10] HMM updates for 5.1
On Wed, Mar 13, 2019 at 09:10:04AM -0700, Andrew Morton wrote:
> On Tue, 12 Mar 2019 21:27:06 -0400 Jerome Glisse <jglisse@...hat.com> wrote:
>
> > Andrew you will not be pushing this patchset in 5.1 ?
>
> I'd like to. It sounds like we're converging on a plan.
>
> It would be good to hear more from the driver developers who will be
> consuming these new features - links to patchsets, review feedback,
> etc. Which individuals should we be asking? Felix, Christian and
> Jason, perhaps?
At least the Mellanox driver patch looks like a good improvement:
https://patchwork.kernel.org/patch/10786625/
5 files changed, 202 insertions(+), 452 deletions(-)
In fact it hollows out the 'umem_odp' driver abstraction we already
had in the RDMA core.
So, I fully expect to see this API used in mlx5 and RDMA-core after it
is merged.
We've done some testing now, and there are still some outstanding
questions on the driver parts, but I haven't seen anything
fundamentally wrong with HMM mirror come up.
Jason
Powered by blists - more mailing lists