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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 17 Jan 2019 08:50:57 -0800
From:   Dan Williams <>
To:     Jeff Moyer <>
Cc:     Dave Hansen <>,
        Tom Lendacky <>,
        Fengguang Wu <>,
        Dave Hansen <>,
        linux-nvdimm <>,
        Takashi Iwai <>,
        Ross Zwisler <>,
        Linux Kernel Mailing List <>,
        Linux MM <>, Michal Hocko <>,
        Yaowei Bai <>,
        "Huang, Ying" <>,
        Bjorn Helgaas <>,
        Andrew Morton <>,
        Borislav Petkov <>
Subject: Re: [PATCH 0/4] Allow persistent memory to be used like normal RAM

On Thu, Jan 17, 2019 at 8:29 AM Jeff Moyer <> wrote:
> Dave Hansen <> writes:
> > Persistent memory is cool.  But, currently, you have to rewrite
> > your applications to use it.  Wouldn't it be cool if you could
> > just have it show up in your system like normal RAM and get to
> > it like a slow blob of memory?  Well... have I got the patch
> > series for you!
> So, isn't that what memory mode is for?

That's a hardware cache that privately manages DRAM in front of PMEM.
It benefits from some help from software [1].

> Why do we need this code in the kernel?

This goes further and enables software managed allocation decisions
with the full DRAM + PMEM address space.


Powered by blists - more mailing lists