aboutsummaryrefslogtreecommitdiffstats
path: root/net/unix/af_unix.c
diff options
context:
space:
mode:
authorDan Williams <[email protected]>2025-02-04 04:24:29 +0000
committerDave Jiang <[email protected]>2025-02-04 20:48:19 +0000
commitbe5cbd0840275c68b3b7d0685d7acc26436c0d99 (patch)
tree93e755d716d55e99d54c33d062bc5602d126a993 /net/unix/af_unix.c
parentcxl: Make cxl_dpa_alloc() DPA partition number agnostic (diff)
downloadkernel-be5cbd0840275c68b3b7d0685d7acc26436c0d99.tar.gz
kernel-be5cbd0840275c68b3b7d0685d7acc26436c0d99.zip
cxl: Kill enum cxl_decoder_mode
Now that the operational mode of DPA capacity (ram vs pmem... etc) is tracked in the partition, and no code paths have dependencies on the mode implying the partition index, the ambiguous 'enum cxl_decoder_mode' can be cleaned up, specifically this ambiguity on whether the operation mode implied anything about the partition order. Endpoint decoders simply reference their assigned partition where the operational mode can be retrieved as partition mode. With this in place PMEM can now be partition0 which happens today when the RAM capacity size is zero. Dynamic RAM can appear above PMEM when DCD arrives, etc. Code sequences that hard coded the "PMEM after RAM" assumption can now just iterate partitions and consult the partition mode after the fact. Reviewed-by: Ira Weiny <[email protected]> Reviewed-by: Alejandro Lucero <[email protected]> Reviewed-by: Dave Jiang <[email protected]> Signed-off-by: Dan Williams <[email protected]> Reviewed-by: Jonathan Cameron <[email protected]> Tested-by: Alejandro Lucero <[email protected]> Link: https://patch.msgid.link/173864306972.668823.3327008645125276726.stgit@dwillia2-xfh.jf.intel.com Signed-off-by: Dave Jiang <[email protected]>
Diffstat (limited to 'net/unix/af_unix.c')
0 files changed, 0 insertions, 0 deletions