linux-kernel - Re: [RFC PATCH] LTTng relay buffer allocation, read, write

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <33307c790809301244x40218be6of61b53104b8d7da3@mail.gmail.com>
Date:	Tue, 30 Sep 2008 12:44:08 -0700
From:	"Martin Bligh" <mbligh@...gle.com>
To:	"Mathieu Desnoyers" <mathieu.desnoyers@...ymtl.ca>
Cc:	"Steven Rostedt" <rostedt@...dmis.org>,
	"Peter Zijlstra" <a.p.zijlstra@...llo.nl>,
	linux-kernel@...r.kernel.org, prasad@...ux.vnet.ibm.com,
	"Linus Torvalds" <torvalds@...ux-foundation.org>,
	"Thomas Gleixner" <tglx@...utronix.de>, od@...e.com,
	"Frank Ch. Eigler" <fche@...hat.com>,
	"Andrew Morton" <akpm@...ux-foundation.org>, hch@....de,
	"David Wilder" <dwilder@...ibm.com>,
	"Tom Zanussi" <zanussi@...cast.net>
Subject: Re: [RFC PATCH] LTTng relay buffer allocation, read, write

> You are actually using them to put redundant information that could be
> encoded differently and thus save 4 bits per event records, more or less
> what will be needed by most tracers (15 IDs, 1 reserved for an extended
> ID field).

You have 15 event types that are useful with no data payload at all?

> So the fact that you use them does not mean they are really required,
> and I don't think such duplicated information actually makes things more
> solid. Maybe just more obscure ?

This is all over 1 bit of information, right? Since you need at least 1 for
the timestamp stuff.
--
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/