| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Fri, 26 Sep 2008 06:47:27 -0400 (EDT) From: Steven Rostedt <rostedt@...dmis.org> To: Peter Zijlstra <peterz@...radead.org> cc: Mathieu Desnoyers <compudj@...stal.dyndns.org>, Masami Hiramatsu <mhiramat@...hat.com>, LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>, Andrew Morton <akpm@...ux-foundation.org>, prasad@...ux.vnet.ibm.com, Linus Torvalds <torvalds@...ux-foundation.org>, "Frank Ch. Eigler" <fche@...hat.com>, David Wilder <dwilder@...ibm.com>, hch@....de, Martin Bligh <mbligh@...gle.com>, Christoph Hellwig <hch@...radead.org>, Steven Rostedt <srostedt@...hat.com> Subject: Re: [RFC PATCH v4] Unified trace buffer On Fri, 26 Sep 2008, Peter Zijlstra wrote: > > > > You could also fallback on a 2-level page array when buffer size is > > > 64MB. The cost is mainly a supplementary pointer dereference, but one > > more should not make sure a big difference overall. > > I'm still not sure why we don't just link the pages using the page > frames, we don't need the random access, do we? Hmm, but this does make changing the buffer size much easier. I'll think about it and perhaps try it out. If I can tidy it up nicer than the ftrace code, then I may include it for v1. -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists