summaryrefslogtreecommitdiffstats
path: root/drivers/sn
diff options
context:
space:
mode:
authorDan Williams <dan.j.williams@intel.com>2016-10-01 02:28:58 +0200
committerDan Williams <dan.j.williams@intel.com>2016-10-07 18:20:53 +0200
commita1f3e4d6a0c322eb3e7fdfcc9facdcdf19130434 (patch)
treec737905cc17b5dd0f5b6015f1e0a0fcee0301a73 /drivers/sn
parentlibnvdimm, namespace: sort namespaces by dpa at init (diff)
downloadlinux-a1f3e4d6a0c322eb3e7fdfcc9facdcdf19130434.tar.xz
linux-a1f3e4d6a0c322eb3e7fdfcc9facdcdf19130434.zip
libnvdimm, region: update nd_region_available_dpa() for multi-pmem support
The free dpa (dimm-physical-address) space calculation reports how much free space is available with consideration for aliased BLK + PMEM regions. Recall that BLK capacity is allocated from high addresses and PMEM is allocated from low addresses in their respective regions. nd_region_available_dpa() accounts for the fact that the largest encroachment (lowest starting address) into PMEM capacity by a BLK allocation limits the available capacity to that point, regardless if there is BLK allocation hole at a higher address. Similarly, for the multi-pmem case we need to track the largest encroachment (highest ending address) of a PMEM allocation in BLK capacity regardless of whether there is an allocation hole that a BLK allocation could fill at a lower address. Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Diffstat (limited to 'drivers/sn')
0 files changed, 0 insertions, 0 deletions