On 11/13/2015 06:00 PM, Toshi Kani wrote: <> > > Agreed. memory_add_physaddr_to_nid() uses the SRAT info, which does not work > with the NFIT case. > Thanks Toshi, I did not know that NFIT would not work. (As I already ranted NFIT is hard to find) Would it be hard to fix? I mean the way it is today NvDIMM is always put at the *end* of the NUMA address range, so all the NUMA boundaries (start) are there, all we need is to make sure max_pfn is advanced behind the last NvDIMM range. (Ok and we might have a slight problem with an NFIT only Node, where there is no volatile memory at all) I think it is worth fixing there are surprising places this might be used. I know that it works with type-12 and emulated pmem. (Once I set up my NFIT QEMU I'll see what I can find) > Thanks, > -Toshi > Thanks Boaz -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
