On Thu, Dec 19, 2013 at 09:53:44AM +0200, Alexander Shishkin wrote: > Yes and some implementations of PT have the same issue, but you can do a > sufficiently large high order allocation and map it to userspace and > still no copying (or parsing/decoding) in kernel space required.
What's sufficiently large? The largest we could possibly allocate is something like 4k^11 which is 8M or so. That's not all that big given you keep saying it generates in the order of 100 MB/s. Also, 'some implementations', that sounds like a fail right there. Why are there already different implementations, and some which such stupid design, of something this new? How about just saying NO to the ones that requires physically contiguous allocations? -- 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/
