Re: [PATCH 3/3] perf record: mmap output file

[Peter Zijlstra]

On Tue, Oct 15, 2013 at 06:06:46PM +0200, Ingo Molnar wrote:
> 
> splice() is very fast and should be able to process a lot of pages in one 
> go, so the feedback loop should be pretty weak. mmap() triggers kernel 
> code as well, every time we run out of the 64 MB window we got to remap 
> it, right?
> 
> But that's all just theory - I think non-temporal stores have a pretty 
> good chance of being a very good solution as well.

The first write to a fresh page will also cause kernel code to be ran. We fault
and run mk_write, which will end up doing block allocation etc..
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/