All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dipankar Sarma <dipankar@gamebox.net>
To: "Martin J. Bligh" <fletch@aracnet.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@zip.com.au>
Subject: Re: kernbench-16 on 2.5.59 vs 2.5.59-mm6
Date: Tue, 28 Jan 2003 00:18:26 +0530	[thread overview]
Message-ID: <20030128001826.A12113@dikhow> (raw)
In-Reply-To: <20030127174015$5cfa@gated-at.bofh.it>; from fletch@aracnet.com on Mon, Jan 27, 2003 at 06:40:15PM +0100

On Mon, Jan 27, 2003 at 06:40:15PM +0100, Martin J. Bligh wrote:
> Going from 59 to 59-mm6, I get:
> 
> Kernbench-16:
>                                    Elapsed        User      System         CPU
>                         2.5.59       47.45      568.02      143.17     1498.17
>                     2.5.59-mm6       47.18      567.15      138.62     1495.50
> 
> Summary: Scheduler stuff seems like a wash (schedule -> do_schedule). 
> Seems to be some sort of rearrangement of the dcache stuff which 
> appears to be mildly beneficial (what's going in there?). 
> 
> diffprofile (+ gets worse, - gets better).
> 
> 2023 do_schedule
> 485 dentry_open
> 289 .text.lock.file_table

Looks like you are getting hit by contention on files_lock. I have
been messing around with some code to split up the files_lock, but
I can't seem to get the locking in the tty layer right.

Hmm.. .text.lock.namei is probably dcache_lock. -mms no longer has
dcache_rcu, so not quite sure what helped you here.


Thanks
Dipankar

       reply	other threads:[~2003-01-27 18:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030127174015$5cfa@gated-at.bofh.it>
2003-01-27 18:48 ` Dipankar Sarma [this message]
2003-01-27 17:36 kernbench-16 on 2.5.59 vs 2.5.59-mm6 Martin J. Bligh
2003-01-28  0:22 ` William Lee Irwin III

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=20030128001826.A12113@dikhow \
    --to=dipankar@gamebox.net \
    --cc=akpm@zip.com.au \
    --cc=fletch@aracnet.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.