Hi Paul, Regarding slide 31 and your comment about adding yellow NVDIMM on the left side of the client, if we are talking about userspace processes, than I would definitely say yes. I assume that the userspace libfabric will have a shared memory provider that uses mmapped bounce buffer in the worst case and single-copy mechanisms such as Linux’s Cross Memory Attach (CMA) or SGI’s XPMEM. Because the processes have different address spaces and each process will end up with a copy of the data, using message queues and RMA make sense.
In the kernel, however, there is a single address space and I am not sure if having two copies is beneficial in any way. If so, then I am not sure if it makes sense to access local resources via kfabric. Scott > On Feb 2, 2016, at 10:54 AM, Paul Grun <[email protected]> wrote: > > Incorporated comments from Bernard and Stan > > > Cray Inc. > Office: (503) 620-8757 > Mobile: (503) 703-5382 > > <kfabric-maintainer > discussion__2016_0201.pptx>_______________________________________________ > ofiwg mailing list > [email protected] > http://lists.openfabrics.org/mailman/listinfo/ofiwg _______________________________________________ ofiwg mailing list [email protected] http://lists.openfabrics.org/mailman/listinfo/ofiwg
