On Mon, Dec 05, 2016 at 12:27:20PM -0700, Logan Gunthorpe wrote:
On 05/12/16 12:14 PM, Jason Gunthorpe wrote:
>But CMB sounds much more like the GPU case where there is a
>specialized allocator handing out the BAR to consumers, so I'm not
>sure a general purpose chardev makes a lot of sense?
I don't think it will ever need to be as complicated as the GPU case. There
will probably only ever be a relatively small amount of memory behind the
CMB and really the only users are those doing P2P work. Thus the specialized
allocator could be pretty simple and I expect it would be fine to just
return -ENOMEM if there is not enough memory.
NVMe might have to deal with pci-e hot-unplug, which is a similar
problem-class to the GPU case..
In any event the allocator still needs to track which regions are in
use and be able to hook 'free' from userspace. That does suggest it
should be integrated into the nvme driver and not a bolt on driver..