linux-kernel - Re: [RFC PATCH 0/2] cxl: BG operations and device sanitation

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20220804200712.gaiswmkjsa3pnkc5@offworld>
Date:   Thu, 4 Aug 2022 13:07:12 -0700
From:   Davidlohr Bueso <dave@...olabs.net>
To:     Dave Jiang <dave.jiang@...el.com>
Cc:     linux-cxl@...r.kernel.org, dan.j.williams@...el.com,
        bwidawsk@...nel.org, Jonathan.Cameron@...wei.com,
        ira.weiny@...el.com, alison.schofield@...el.com,
        vishal.l.verma@...el.com, a.manzanares@...sung.com,
        mcgrof@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 0/2] cxl: BG operations and device sanitation

On Thu, 04 Aug 2022, Dave Jiang wrote:

>>From the operational sense everything looks good to me. As for the
>polling delay on overwrite, with pre-CXL pmem on Optane, we've
>discovered that overwrite can take a long time depending on the size.
>Sometimes MANY hours if the size is really large. We just opted to
>increment the polling interval as time went on [1] instead of based on
>size.

Thanks for having a look. Sure, we can do that, I have no particular attachment
to doing it based on size (it's just the way it occured to me). I am curious,
though: While regardless of size vs time based estimates, are the numbers
expected to be similar for volatile regions? All these numbers being from
nvdimm DSM docs.

Thanks,
Davidlohr