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
| ||
|
Date: Mon, 27 Oct 2008 20:21:58 -0400 (EDT) From: Steven Rostedt <rostedt@...dmis.org> To: Theodore Tso <tytso@....edu> cc: Mike Snitzer <snitzer@...il.com>, linux-ext4@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org> Subject: Re: why unlikely(rsv) in ext3_clear_inode()? On Mon, 27 Oct 2008, Theodore Tso wrote: > On Mon, Oct 27, 2008 at 07:32:11PM -0400, Steven Rostedt wrote: > > Attached is a patch that I used for counting. > > > > Here's my results: > > # cat /debug/tracing/ftrace_null > > 45 > > # cat /debug/tracing/ftrace_nonnull > > 7 > > > > Ah, seems that there is cases where it is nonnull more often. Anyway, it > > obviously is not a fast path (total of 52). Even if it was all null, it is > > not big enough to call for the confusion. > > Silly question --- what was your test workload? Hehe, I just booted the box. The counting started right away, so I just looked at the work load. Anyway, I'm writing a generic "unlikely" profiler that should make Andrew happy. And this will also catch this case as well. -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists