| 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: <1196799863.6073.22.camel@localhost> Date: Tue, 04 Dec 2007 12:24:23 -0800 From: Dave Hansen <haveblue@...ibm.com> To: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca> Cc: "Frank Ch. Eigler" <fche@...hat.com>, akpm@...ux-foundation.org, linux-kernel@...r.kernel.org, linux-mm@...ck.org, mbligh@...gle.com Subject: Re: [RFC PATCH] LTTng instrumentation mm (updated) On Tue, 2007-12-04 at 15:05 -0500, Mathieu Desnoyers wrote: > * Dave Hansen (haveblue@...ibm.com) wrote: > > On Tue, 2007-12-04 at 14:25 -0500, Mathieu Desnoyers wrote: > > > > > > - I also dump the equivalent of /proc/swaps (with kernel internal > > > information) at trace start to know what swap files are currently > > > used. > > > > What about just enhancing /proc/swaps so that this information can be > > useful to people other than those doing traces? > > It includes an in-kernel struct file pointer, exporting it to userspace > would be somewhat ugly. What about just exporting the 'type' field that we use to index into swap_info[]? As far as /proc goes, it may not be _ideal_ for your traces, but it sure beats not getting the information out at all. ;) I guess I'm just not that familiar with the tracing requirements and I can't really assess whether what you're asking for is reasonable, or horrible over-engineering. Dunno. -- Dave -- 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