| 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
| ||
|
Message-ID: <1291652255.16223.29.camel@gandalf.stny.rr.com> Date: Mon, 06 Dec 2010 11:17:35 -0500 From: Steven Rostedt <rostedt@...dmis.org> To: Andi Kleen <andi@...stfloor.org> Cc: Ted Ts'o <tytso@....edu>, David Sharp <dhsharp@...gle.com>, linux-kernel@...r.kernel.org, mrubin@...gle.com Subject: Re: [Patch 00/15] Reduce tracing payload size. On Mon, 2010-12-06 at 15:58 +0100, Andi Kleen wrote: > On Mon, Dec 06, 2010 at 08:56:37AM -0500, Ted Ts'o wrote: > > On Mon, Dec 06, 2010 at 02:22:00PM +0100, Andi Kleen wrote: > > > David Sharp <dhsharp@...gle.com> writes: > > > > > > > > These patches are just a start to shrinking the size of trace events. I am > > > > planning to also make small versions of trace events that are used when > > > > CONFIG_SMALL_TRACES is enabled. I'm also open to discussion of other ways to > > > > shrink event sizes. > > > > > > Maybe the simplest would be to lzo them as they get logged? > > > I assume you already considered that? > > > > The tracing subsystem is supposed to be extremely low-overhead. > > Compressiong the event log would add considerable CPU overhead. If we > > lzo as a rule of thumb is about as expensive as 3x memcpy() > That's not really expensive. Usually the most expensive thing in the trace is the memcpy(). Which is why we try to do it only once. -- 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