On Tue, May 05, 2015 at 05:32:21PM -0400, Tom Talpey wrote: > >But that whole painpoint only existist for userspace ib verbs consumers. > >And in-kernel consumer fits into the "pinned" or "wired" categegory, > >as any local DMA requires it. > > True, but I think there's a bit more to it. For example, the buffer > cache is pinned, but the data on the page isn't dedicated to an i/o, > it's shared among file-layer stuff. Of course, a file-layer RDMA > protocol needs to play by those rules, but I'll use it as a warning > that it's not always simple. Actually there is no buffer cache anymore, and the page cache now keeps pages under writeback stable, that is doesn't allow modifications while the page is written back. Not that it matters, as both direct I/O for filesystems or SG_IO for block devices allows I/O to user pages that can be modified while dma is in progress. So pretty much every in kernel user has to deal with this case, maybe with the exception of network protocols. > >The contiguous requirements isn't something we can alway guarantee. > >While a lot of I/O will have that form the form where there are holes > >can happen, although it's not common. > > Yeah, and the important takeaway is that a memory registration API > can't hide this - meaning, the upper layer needs to address it (hah!). > Often, once an upper layer has to do this, it can do better by doing > it itself. But that's perhaps too philosophical here. Let me just > say that transparency has proved to be the enemy of performance. Yes, I don't think that something that should be worked around at an API at a low level. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
