Skip to contentSkip to conversation

Balancing near the locking cliff, with some numbers

DISCUSSION [email protected] 2 participants 2 messages Nov 14, 2005 – Nov 15, 2005

lore
Share & tools
lore
#0 lore raw
Quoted 9 lines

open:
locks: 106 sems: 32 atomics: 50 rwlocks: 30 irqsaves: 89 barriers: 47 read:
locks: 52 sems: 0 atomics: 16 rwlocks: 12 irqsaves: 69 barriers: 11 write:
locks: 38 sems: 4 atomics: 20 rwlocks: 8 irqsaves: 42 barriers: 12 page fault:
locks: 4 sems: 2 atomics: 2 rwlocks: 0 irqsaves: 9 barriers: 0

Quoted 8 lines

open: open a file on ext3
read: read a cache cold file from disk
write: write a new file
page fault: fault in an empty page

It read random files from /usr/X11R6/bin to get something out of cache. The bin directory was likely all in dcache and the directory lpages in buffer cache.

This is very interesting data, thank you!
This is using the standard IDE driver?
And the path names were absolute?

What would be really nice is a full trace of the locks acquired so we can look for specific problems. (I can see the OpenSolaris folks puffing up to crow about dtrace already.)

Barring that, a few variants like hot-cache cases, different file systems (includig tmpfs), and different device drivers would be informative. (You could also try the different ext3 journalling modes.)

I'm not sre quite how you did this, but assuming you just installed global counters via macros and ran the test by booting with init=, you could do a bit better with a hook that would log 1000 filename/line number pairs, stopping when the log was full, and another to read and clear the log.

#1 lore raw

Mr Linux,

Quoted 3 lines · On Monday 14 November 2005 13:03, [email protected] wrote:

This is very interesting data, thank you!
This is using the standard IDE driver?
And the path names were absolute?

Yes. No.

Quoted 8 lines

What would be really nice is a full trace of the locks acquired so we can look for specific problems. (I can see the OpenSolaris folks puffing up to crow about dtrace already.)

Barring that, a few variants like hot-cache cases, different file systems (includig tmpfs), and different device drivers would be informative. (You could also try the different ext3 journalling modes.)

I have no plans to generate such data right now, but if you want to
do it yourself I can send you my patches as a starting point. Should be easy enough using relayfs.

Quoted 2 lines

I'm not sre quite how you did this, but assuming you just installed global counters via macros

per process counters.

Quoted 1 line

and ran the test by booting with init=

from a normal shell in a running system

-Andi