| 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: <1242594505.6327.3.camel@localhost.localdomain> Date: Sun, 17 May 2009 17:08:25 -0400 From: Jon Masters <jonathan@...masters.org> To: Steven Rostedt <rostedt@...dmis.org> Cc: linux-kernel <linux-kernel@...r.kernel.org> Subject: [tracing] ring_buffer question Steven, Is there any reason you can think of why we don't just generalize kernel/trace/ring_buffer into kernel/ring_buffer, remove the static per_cpu buffer allocation and have this available for non-tracing? As it is, trace buffers only store generic data and the design (swap on read) is very nicely done for many other ring buffer uses. Jon. -- 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