public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Mala Anand <manand@us.ibm.com>,
	Benjamin LaHaise <bcrl@redhat.com>,
	alan@lxorguk.ukuu.org.uk, Bill Hartner <bhartner@us.ibm.com>,
	davem@redhat.com, linux-kernel@vger.kernel.org,
	lse-tech@lists.sourceforge.net,
	lse-tech-admin@lists.sourceforge.net
Subject: Re: [Lse-tech] Re: (RFC): SKB Initialization
Date: Thu, 22 Aug 2002 15:05:25 -0700	[thread overview]
Message-ID: <20020822220525.GZ21685@holomorphy.com> (raw)
In-Reply-To: <3D653543.6000403@us.ibm.com>

On Thu, Aug 22, 2002 at 12:02:27PM -0700, Dave Hansen wrote:
> You can see the entire readprofile here:
> http://www.sr71.net/~specweb99/run-specweb-100sec-2400-2.5.31-bk+4-kmap-08-22-2002-11.20.17/
> http://www.sr71.net/~specweb99/run-specweb-100sec-2400-2.5.31-bk+4-kmap-mala-08-22-2002-11.44.25/
> No, I don't know why I have so much idle time.

Hmm, I found that tiobench was spending a lot of time idle due to
__wait_on_inode() and get_request_wait(). I bumped up the size of
the inode wait table to 1024 and the request queue size to 16384
and saw that most of them then spent their time stuck on ->i_sem
during the initial open of the file they were going to pound on
for the duration of the run.

I determined this by just ^C'ing with kgdb and backtracing various
"stuck" processes. I think various profiling patches might be able to
give you an idea of what people are going to sleep on too.


Cheers,
Bill

  parent reply	other threads:[~2002-08-22 22:04 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-22 17:22 [Lse-tech] Re: (RFC): SKB Initialization Mala Anand
2002-08-22 18:32 ` Benjamin LaHaise
2002-08-22 19:02 ` Dave Hansen
2002-08-22 20:58   ` [Ibm-specweb99] " Nivedita Singhvi
2002-08-22 22:05   ` William Lee Irwin III [this message]
2002-08-23 19:09 ` Bill Hartner
  -- strict thread matches above, loose matches on Subject: below --
2002-08-23 14:44 Mala Anand
2002-08-23 16:39 ` Dave Hansen
2002-08-23 20:12   ` Bill Hartner
2002-08-23 20:30     ` Dave Hansen
2002-08-23 23:36       ` Troy Wilson
2002-08-23 20:51     ` Rick Lindsley
2002-08-23 22:41   ` David S. Miller
2002-08-23 23:14 Mala Anand
2002-08-23 23:38 Mala Anand
2002-08-23 23:55 ` David S. Miller
2002-08-25 16:17 jamal
2002-08-25 22:51 ` David S. Miller
2002-08-25 20:12 Mala Anand
2002-08-26  1:02 ` jamal
2002-08-26 13:04 Mala Anand
2002-08-26 19:28 ` Robert Olsson
2002-08-27 10:17 ` jamal
2002-08-27  2:53 Mala Anand
2002-08-27 13:18 Mala Anand
2002-08-27 15:49 ` jamal
2002-09-03  3:47 Mala Anand

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=20020822220525.GZ21685@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bcrl@redhat.com \
    --cc=bhartner@us.ibm.com \
    --cc=davem@redhat.com \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech-admin@lists.sourceforge.net \
    --cc=lse-tech@lists.sourceforge.net \
    --cc=manand@us.ibm.com \
    /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