From: Andi Kleen <ak@suse.de>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: linux-kernel@vger.kernel.org, dipankar@in.ibm.com
Subject: Re: Balancing near the locking cliff, with some numbers
Date: Sat, 5 Nov 2005 05:46:07 +0100 [thread overview]
Message-ID: <200511050546.07944.ak@suse.de> (raw)
In-Reply-To: <20051105031218.GK7992@ftp.linux.org.uk>
On Saturday 05 November 2005 04:12, Al Viro wrote:
> On Fri, Nov 04, 2005 at 08:56:59PM +0100, Andi Kleen wrote:
> > open:
> > locks: 106 sems: 32 atomics: 50 rwlocks: 30 irqsaves: 89 barriers: 47
>
> How long was the pathname and how much of that was in cache?
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.
-Andi
next prev parent reply other threads:[~2005-11-05 4:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 19:56 Balancing near the locking cliff, with some numbers Andi Kleen
2005-11-05 3:12 ` Al Viro
2005-11-05 4:46 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-14 12:03 linux
2005-11-15 3:26 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200511050546.07944.ak@suse.de \
--to=ak@suse.de \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ftp.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox