From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751418AbdCRERs convert rfc822-to-8bit (ORCPT ); Sat, 18 Mar 2017 00:17:48 -0400 Received: from mx1.redhat.com ([209.132.183.28]:45298 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750712AbdCRERq (ORCPT ); Sat, 18 Mar 2017 00:17:46 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 330F58E3F0 Authentication-Results: ext-mx01.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx01.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=jglisse@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 330F58E3F0 Date: Fri, 17 Mar 2017 23:54:02 -0400 (EDT) From: Jerome Glisse To: John Hubbard Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, Naoya Horiguchi , David Nellans Message-ID: <511871248.8852779.1489809242452.JavaMail.zimbra@redhat.com> In-Reply-To: References: <1489778823-8694-1-git-send-email-jglisse@redhat.com> <1489778823-8694-3-git-send-email-jglisse@redhat.com> Subject: Re: [HMM 2/2] hmm: heterogeneous memory management documentation MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT X-Originating-IP: [10.10.123.15] Thread-Topic: heterogeneous memory management documentation Thread-Index: /otW0RghbS88b0dxXMMlBUpG9v358A== X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.25]); Sat, 18 Mar 2017 03:54:03 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > On 03/17/2017 12:27 PM, Jérôme Glisse wrote: > > This add documentation for HMM (Heterogeneous Memory Management). It > > presents the motivation behind it, the features necessary for it to > > be usefull and and gives an overview of how this is implemented. > > For this patch, I will leave it to others to decide how to proceed, given the > following: > > 1. This hmm.txt has a lot of critical information in it. > > 2. It is, however, more of a first draft than a final draft: lots of errors > in each sentence, and > lots of paragraphs that need re-doing, for example. After a quick pass > through a few other > Documentation/vm/*.txt documents to gage the quality bar, I am inclined to > recommend (or do) a > second draft of this, before submitting it. > > Since I'm the one being harsh here (and Jerome, you already know I'm harsh! > haha), I can provide a > second draft. But it won't look much like the current draft, so brace > yourself before saying yes... :) Feel free to take a stab at it :) Cheers, Jérôme