Alistair Popple writes:
> "Huang, Ying" writes:
>
>> Alistair Popple writes:
>>
>>> "Huang, Ying" writes:
>>>
>> And, I don't think that we are forced to use the general notifier
>> chain interface in all memory device drivers. If the memory device
>> driver has better
"Huang, Ying" writes:
> Alistair Popple writes:
>
>> "Huang, Ying" writes:
>>
> And, I don't think that we are forced to use the general notifier
> chain interface in all memory device drivers. If the memory device
> driver has better understanding of the memory device, it can
Alistair Popple writes:
> "Huang, Ying" writes:
>
The other way (suggested by this series) is to make dax/kmem call a
notifier chain, then CXL CDAT or ACPI HMAT can identify the type of
device and calculate the distance if the type is correct for them. I
don't think that
"Huang, Ying" writes:
>>> The other way (suggested by this series) is to make dax/kmem call a
>>> notifier chain, then CXL CDAT or ACPI HMAT can identify the type of
>>> device and calculate the distance if the type is correct for them. I
>>> don't think that it's good to make dax/kem to know
Alistair Popple writes:
> "Huang, Ying" writes:
>
>> Hi, Alistair,
>>
>> Thanks a lot for comments!
>>
>> Alistair Popple writes:
>>
>>> Huang Ying writes:
>>>
The abstract distance may be calculated by various drivers, such as
ACPI HMAT, CXL CDAT, etc. While it may be used by
5 matches
Mail list logo
