| 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: <20101206135637.GC8135@thunk.org> Date: Mon, 6 Dec 2010 08:56:37 -0500 From: Ted Ts'o <tytso@....edu> To: Andi Kleen <andi@...stfloor.org> Cc: David Sharp <dhsharp@...gle.com>, rostedt@...dmis.org, linux-kernel@...r.kernel.org, mrubin@...gle.com Subject: Re: [Patch 00/15] Reduce tracing payload size. 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 can shrink the trace events by being more careful about unnecessary padding, and not logging fields that aren't needed, it's all win.... The problem of course with the latter is that different people will have disagreements about what is needed or not. And even adding conditionals will slow down the tracing hotpath. - Ted -- 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