linux-kernel - Re: Hot ADD using CXL1.1 host

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 for Android: free password hash cracker in your pocket

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

Message-ID: <63d94ad9901a1_8e2c294bc@dwillia2-mobl3.amr.corp.intel.com.notmuch>
Date:   Tue, 31 Jan 2023 09:07:37 -0800
From:   Dan Williams <dan.j.williams@...el.com>
To:     Shesha Sreenivasamurthy <sheshas@...il.com>,
        Dan Williams <dan.j.williams@...el.com>
CC:     <linux-kernel@...r.kernel.org>, <linux-cxl@...r.kernel.org>
Subject: Re: Hot ADD using CXL1.1 host

Shesha Sreenivasamurthy wrote:
[..]
> There seems to be some instability in using DAX. When the system is
> given all the device memory using efi=nosoftreserve, the stressapptest
> (https://github.com/stressapptest/stressapptest) runs for an extended
> period of time. However, when the system is booted without
> efi=nosoftreserve, and assigned the special purpose memory to
> system-ram using daxctl, the system crashes after some time (20-30
> mins). Is there any known instabilities when using DAX?

One difference with late binding of memory is where kernel data
structures are allocated. So the stress profile can change based on
kernel activity. Otherwise there is no known instability with delaying
the online of memory.