On Thu, Sep 9, 2021 at 8:58 AM Ben Widawsky <[email protected]> wrote: > > On 21-09-08 22:11:58, Dan Williams wrote: > > Add a definition of the CXL 2.0 region label format. Note this is done > > as a separate patch to make the next patch that adds namespace label > > support easier to read. > > > > Reported-by: Jonathan Cameron <[email protected]> > > Reviewed-by: Jonathan Cameron <[email protected]> > > Signed-off-by: Dan Williams <[email protected]> > > --- > > drivers/nvdimm/label.h | 32 ++++++++++++++++++++++++++++++++ > > 1 file changed, 32 insertions(+) > > Wondering how awkward it's going to be to use this in the cxl region driver. > Is > the intent to push all device based reads/writes to labels happen in > drivers/nvdimm?
I am looking at it from the perspective that namespace provisioning and assembly will need to consult region details. So drivers/nvdimm/ needs to have region-label awareness regardless. Now, when the CXL side wants to provision a region, it will also need to coordinate label area access with any namespace provisioning operations that might be happening on other regions that the CXL device is contributing. Both of those lead me to believe that CXL should just request the nvdimm sub-system to update labels to keep all the competing label operations and cached label data in-sync.
