| 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: <y0mve7ez2y3.fsf@ton.toronto.redhat.com> Date: Tue, 04 Dec 2007 14:15:32 -0500 From: fche@...hat.com (Frank Ch. Eigler) To: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca> Cc: Dave Hansen <haveblue@...ibm.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) Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca> writes: > [...] >> > We would like to be able to tell which swap file the information has >> > been written to/read from at any given time during the trace. >> >> Oh, tracing is expected to be on at all times? I figured someone would >> encounter a problem, then turn it on to dig down a little deeper, then >> turn it off. > > Yep, it can be expected to be on at all times, especially on production > systems using "flight recorder" tracing to record information in a > circular buffer [...] Considering how early in the boot sequence swap partitions are activated, it seems optimistic to assume that the monitoring equipment will always start up in time to catch the initial swapons. It would be more useful if a marker parameter was included in the swap events to let a tool/user map to /proc/swaps or a file name. - FChE -- 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