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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 4 Dec 2006 13:21:29 +0100
From:	bert hubert <>
To:	Bill Huey <>
Cc:	Ingo Molnar <>,
Subject: Re: [PATCH 0/4] lock stat for 2.6.19-rt1

On Sun, Dec 03, 2006 at 05:53:23PM -0800, Bill Huey wrote:

> [8264, 996648, 0]		{inode_init_once, fs/inode.c, 196}
> [8552, 996648, 0]		{inode_init_once, fs/inode.c, 193}

Impressive, Bill!

How tightly is your work bound to -rt? Iow, any chance of separating the
two? Or should we even want to?

> The first column is the number of the times that object was contented against.
> The second is the number of times this lock object was initialized. The third
> is the annotation scheme that directly attaches the lock object (spinlock,
> etc..) in line with the function initializer to avoid the binary tree lookup.

I don't entirely get the third item, can you elaborate a bit?

Do you have a feeling of the runtime overhead?


--      Open source, database driven DNS Software              Open and Closed source services
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists