On Mon, 2 Mar 2015 11:24:04 -0800 Alexei Starovoitov <a...@plumgrid.com> wrote: > well, percentage of tracepoints called from NMI is tiny > comparing to the rest, so assuming nmi context > everywhere is very inefficient. > Like we can use pre-allocated pool of map entries when > tracepoint is called from NMI, but we shouldn't be using > it in other cases. Just like ring buffers and other things > have nmi and non-nmi pools and code paths, it doesn't > make sense to disallow kmalloc all together. > btw, calling kmalloc is _faster_ than taking > objects from cache-cold special nmi only pool.
Please show the numbers and post the tests when stating something like that. -- Steve -- 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/
