Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Thu, 4 Aug 2022 13:07:12 -0700
From:   Davidlohr Bueso <dave@stgolabs.net>
To:     Dave Jiang <dave.jiang@intel.com>
Cc:     linux-cxl@vger.kernel.org, dan.j.williams@intel.com,
        bwidawsk@kernel.org, Jonathan.Cameron@huawei.com,
        ira.weiny@intel.com, alison.schofield@intel.com,
        vishal.l.verma@intel.com, a.manzanares@samsung.com,
        mcgrof@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/2] cxl: BG operations and device sanitation
Message-ID: <20220804200712.gaiswmkjsa3pnkc5@offworld>
References: <20220804045029.2905056-1-dave@stgolabs.net>
 <bcbe1db2-cb8e-1889-2888-f4618d749bd4@intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
In-Reply-To: <bcbe1db2-cb8e-1889-2888-f4618d749bd4@intel.com>
User-Agent: NeoMutt/20220429
Precedence: bulk

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