From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754287AbdBVIQM (ORCPT ); Wed, 22 Feb 2017 03:16:12 -0500 Received: from mail.linuxfoundation.org ([140.211.169.12]:36070 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752842AbdBVIQF (ORCPT ); Wed, 22 Feb 2017 03:16:05 -0500 Date: Wed, 22 Feb 2017 00:16:03 -0800 From: Andrew Morton To: Balbir Singh Cc: =?ISO-8859-1?Q?J=E9r=F4me?= Glisse , linux-kernel@vger.kernel.org, linux-mm@kvack.org, John Hubbard , Naoya Horiguchi , David Nellans Subject: Re: [HMM v17 00/14] HMM (Heterogeneous Memory Management) v17 Message-Id: <20170222001603.162a1209efc06b6c46556383@linux-foundation.org> In-Reply-To: <20170222071915.GE9967@balbir.ozlabs.ibm.com> References: <1485557541-7806-1-git-send-email-jglisse@redhat.com> <20170222071915.GE9967@balbir.ozlabs.ibm.com> X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.28; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 22 Feb 2017 18:19:15 +1100 Balbir Singh wrote: > On Fri, Jan 27, 2017 at 05:52:07PM -0500, J__r__me Glisse wrote: > > Cliff note: HMM offers 2 things (each standing on its own). First > > it allows to use device memory transparently inside any process > > without any modifications to process program code. Second it allows > > to mirror process address space on a device. > > > > Change since v16: > > - move HMM unaddressable device memory to its own radix tree and > > thus find_dev_pagemap() will no longer return HMM dev_pagemap > > - rename HMM migration helper (drop the prefix) and make them > > completely independent of HMM > > > > Migration can now be use to implement thing like multi-threaded > > copy or make use of specific memory allocator for destination > > memory. > > > > Work is under way to use this feature inside nouveau (the upstream > > open source driver for NVidia GPU) either 411 or 4.12 timeframe. > > But this patchset have been otherwise tested with the close source > > driver for NVidia GPU and thus we are confident it works and allow > > to use the hardware for seamless interaction between CPU and GPU > > in common address space of a process. > > > > I also discussed the features with other company and i am confident > > it can be use on other, yet, unrelease hardware. > > > > Please condiser applying for 4.11 > > > > Andrew, do we expect to get this in 4.11/4.12? Just curious. > I'll be taking a serious look after -rc1. The lack of reviewed-by, acked-by and tested-by is a concern. It's rather odd for a patchset in the 17th revision! What's up with that? Have you reviewed or tested the patches?