linux-kernel - Re: [HMM 01/15] hmm: heterogeneous memory management documentation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <3937c1fd-5ac9-a933-9562-98e728a22cfb@nvidia.com>
Date:   Fri, 23 Jun 2017 23:15:56 -0700
From:   John Hubbard <jhubbard@...dia.com>
To:     Jérôme Glisse <jglisse@...hat.com>,
        <akpm@...ux-foundation.org>, <linux-kernel@...r.kernel.org>,
        <linux-mm@...ck.org>
CC:     Dan Williams <dan.j.williams@...el.com>,
        "Kirill A . Shutemov" <kirill.shutemov@...ux.intel.com>
Subject: Re: [HMM 01/15] hmm: heterogeneous memory management documentation

On 05/24/2017 10:20 AM, 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 useful and and gives an overview of how this is implemented.
> 
> Signed-off-by: Jérôme Glisse <jglisse@...hat.com>
> ---
>   Documentation/vm/hmm.txt | 362 +++++++++++++++++++++++++++++++++++++++++++++++
>   MAINTAINERS              |   7 +
>   2 files changed, 369 insertions(+)
>   create mode 100644 Documentation/vm/hmm.txt
> 
> diff --git a/Documentation/vm/hmm.txt b/Documentation/vm/hmm.txt
> new file mode 100644
> index 0000000..a18ffc0
> --- /dev/null
> +++ b/Documentation/vm/hmm.txt
> @@ -0,0 +1,362 @@
> +Heterogeneous Memory Management (HMM)
> +

Some months ago, I made a rash promise to give this document some editing love. I am still 
willing to do that if anyone sees the need, but I put it on the back burner because I 
suspect that the document is already good enough. This is based on not seeing any "I am 
having trouble understanding HMM" complaints.

If that's not the case, please speak up. Otherwise, I'm assuming that all is well in the 
HMM Documentation department.

thanks,
--
John Hubbard
NVIDIA