From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932486AbdEXRx5 (ORCPT ); Wed, 24 May 2017 13:53:57 -0400 Received: from mx1.redhat.com ([209.132.183.28]:57370 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932397AbdEXRxx (ORCPT ); Wed, 24 May 2017 13:53:53 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 01B6837E72 Authentication-Results: ext-mx05.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx05.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=jglisse@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 01B6837E72 Date: Wed, 24 May 2017 13:53:50 -0400 From: Jerome Glisse To: Balbir Singh Cc: "akpm@linux-foundation.org" , "linux-kernel@vger.kernel.org" , linux-mm , John Hubbard , David Nellans Subject: Re: [HMM 00/15] HMM (Heterogeneous Memory Management) v22 Message-ID: <20170524175349.GB24024@redhat.com> References: <20170522165206.6284-1-jglisse@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.8.0 (2017-02-23) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.29]); Wed, 24 May 2017 17:53:53 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 24, 2017 at 11:55:12AM +1000, Balbir Singh wrote: > On Tue, May 23, 2017 at 2:51 AM, Jérôme Glisse wrote: > > Patchset is on top of mmotm mmotm-2017-05-18, git branch: > > > > https://cgit.freedesktop.org/~glisse/linux/log/?h=hmm-v22 > > > > Change since v21 is adding back special refcounting in put_page() to > > catch when a ZONE_DEVICE page is free (refcount going from 2 to 1 > > unlike regular page where a refcount of 0 means the page is free). > > See patch 8 of this serie for this refcounting. I did not use static > > keys because it kind of scares me to do that for an inline function. > > If people strongly feel about this i can try to make static key works > > here. Kirill will most likely want to review this. > > > > > > Everything else is the same. Below is the long description of what HMM > > is about and why. At the end of this email i describe briefly each patch > > and suggest reviewers for each of them. > > > > > > Heterogeneous Memory Management (HMM) (description and justification) > > > > Thanks for the patches! These patches are very helpful. There are a > few additional things we would need on top of this (once HMM the base > is merged) > > 1. Support for other architectures, we'd like to make sure we can get > this working for powerpc for example. As a first step we have > ZONE_DEVICE enablement patches, but I think we need some additional > patches for iomem space searching and memory hotplug, IIRC > 2. HMM-CDM and physical address based migration bits. In a recent RFC > we decided to try and use the HMM CDM route as a route to implementing > coherent device memory as a starting point. It would be nice to have > those patches on top of these once these make it to mm - > https://lwn.net/Articles/720380/ > I intend to post the updated HMM CDM patchset early next week. I am tie in couple internal backport but i should be able to resume work on that this week. Cheers, Jérôme From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt0-f199.google.com (mail-qt0-f199.google.com [209.85.216.199]) by kanga.kvack.org (Postfix) with ESMTP id C91DA6B0292 for ; Wed, 24 May 2017 13:53:54 -0400 (EDT) Received: by mail-qt0-f199.google.com with SMTP id j13so70063736qta.13 for ; Wed, 24 May 2017 10:53:54 -0700 (PDT) Received: from mx1.redhat.com (mx1.redhat.com. [209.132.183.28]) by mx.google.com with ESMTPS id l63si210019qke.55.2017.05.24.10.53.53 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 24 May 2017 10:53:54 -0700 (PDT) Date: Wed, 24 May 2017 13:53:50 -0400 From: Jerome Glisse Subject: Re: [HMM 00/15] HMM (Heterogeneous Memory Management) v22 Message-ID: <20170524175349.GB24024@redhat.com> References: <20170522165206.6284-1-jglisse@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Sender: owner-linux-mm@kvack.org List-ID: To: Balbir Singh Cc: "akpm@linux-foundation.org" , "linux-kernel@vger.kernel.org" , linux-mm , John Hubbard , David Nellans On Wed, May 24, 2017 at 11:55:12AM +1000, Balbir Singh wrote: > On Tue, May 23, 2017 at 2:51 AM, Jerome Glisse wrote: > > Patchset is on top of mmotm mmotm-2017-05-18, git branch: > > > > https://cgit.freedesktop.org/~glisse/linux/log/?h=hmm-v22 > > > > Change since v21 is adding back special refcounting in put_page() to > > catch when a ZONE_DEVICE page is free (refcount going from 2 to 1 > > unlike regular page where a refcount of 0 means the page is free). > > See patch 8 of this serie for this refcounting. I did not use static > > keys because it kind of scares me to do that for an inline function. > > If people strongly feel about this i can try to make static key works > > here. Kirill will most likely want to review this. > > > > > > Everything else is the same. Below is the long description of what HMM > > is about and why. At the end of this email i describe briefly each patch > > and suggest reviewers for each of them. > > > > > > Heterogeneous Memory Management (HMM) (description and justification) > > > > Thanks for the patches! These patches are very helpful. There are a > few additional things we would need on top of this (once HMM the base > is merged) > > 1. Support for other architectures, we'd like to make sure we can get > this working for powerpc for example. As a first step we have > ZONE_DEVICE enablement patches, but I think we need some additional > patches for iomem space searching and memory hotplug, IIRC > 2. HMM-CDM and physical address based migration bits. In a recent RFC > we decided to try and use the HMM CDM route as a route to implementing > coherent device memory as a starting point. It would be nice to have > those patches on top of these once these make it to mm - > https://lwn.net/Articles/720380/ > I intend to post the updated HMM CDM patchset early next week. I am tie in couple internal backport but i should be able to resume work on that this week. Cheers, Jerome -- 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: email@kvack.org