On Fri, 2015-04-24 at 11:58 -0500, Christoph Lameter wrote: > On Fri, 24 Apr 2015, Jerome Glisse wrote: > > > > What exactly is the more advanced version's benefit? What are the features > > > that the other platforms do not provide? > > > > Transparent access to device memory from the CPU, you can map any of the GPU > > memory inside the CPU and have the whole cache coherency including proper > > atomic memory operation. CAPI is not some mumbo jumbo marketing name there > > is real hardware behind it. > > Got the hardware here but I am getting pretty sobered given what I heard > here. The IBM mumbo jumpo marketing comes down to "not much" now.
Ugh ... first nothing we propose precludes using it with explicit memory management the way you want. So I don't know why you have a problem here. We are trying to cover a *different* usage model than yours obviously. But they aren't exclusive. Secondly, none of what we are discussing here is supported by *existing* hardware, so whatever you have is not concerned. There is no CAPI based coprocessor today that provides cachable memory to the system (though CAPI as a technology supports it), and no GPU doing that either *yet*. Today CAPI adapters can own host cache lines but don't expose large swath of cachable local memory. Finally, this discussion is not even specifically about CAPI or its performances. It's about the *general* case of a coherent coprocessor sharing the MMU. Whether it's using CAPI or whatever other technology that allows that sort of thing that we may or may not be able to mention at this point. CAPI is just an example because architecturally it allows that too. Ben. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
