lkml.org 
[lkml]   [2018]   [Mar]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: [PATCH v2 10/10] nvmet: Optionally use PCI P2P memory


On 01/03/18 04:57 PM, Stephen Bates wrote:
>> We don't want to lump these all together without knowing which region you're allocating from, right?
>
> In all seriousness I do agree with you on these Keith in the long term. We would consider adding property flags for the memory as it is added to the p2p core and then the allocator could evolve to intelligently dish it out. Attributes like endurance, latency and special write commit requirements could all become attributes in time. Perhaps one more reason for a central entity for p2p memory allocation so this code does not end up having to go into many different drivers?

Ugh, I don't know... An allocator for PMR is going to be quite a
different animal. It would probably need to look more like a filesystem
given you'd need to access the same regions across reboots. I don't
think it fits the p2pmem paradigm at all. I think it's something
entirely new all together and who knows exactly what it will look like.

Logan

\
 
 \ /
  Last update: 2022-09-17 16:04    [W:0.170 / U:0.876 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site