From: Andrew Morton <akpm@digeo.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.65-mm4
Date: Sun, 23 Mar 2003 19:17:44 -0800 [thread overview]
Message-ID: <20030323191744.56537860.akpm@digeo.com> (raw)
In-Reply-To: <9590000.1048475057@[10.10.2.4]>
"Martin J. Bligh" <mbligh@aracnet.com> wrote:
>
> profile from SDET 64:
SDET is rather irritating because a) nobody has a copy and b) we don't even
know what it does.
>
> 82303 __down
> 42835 schedule
> 31323 __wake_up
> 26435 .text.lock.sched
> 15924 .text.lock.transaction
But judging by this, it's a rebadged dbench. The profile is identical.
Note that the lock_kernel() contention has been drastically reduced and we're
now hitting semaphore contention.
Running `dbench 32' on the quad Xeon, this patch took the context switch rate
from 500/sec up to 125,000/sec.
I've asked Alex to put together a patch for spinlock-based locking in the
block allocator (cut-n-paste from ext2).
That will fix up lock_super(), but I suspect the main problem is the
lock_journal() in journal_start(). I haven't thought about that one yet.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
next prev parent reply other threads:[~2003-03-24 3:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-23 10:06 2.5.65-mm4 Andrew Morton
2003-03-23 17:55 ` 2.5.65-mm4 Alexander Hoogerhuis
2003-03-23 18:16 ` 2.5.65-mm4 Martin J. Bligh
2003-03-23 20:08 ` 2.5.65-mm4 Martin J. Bligh
2003-03-24 3:04 ` 2.5.65-mm4 Martin J. Bligh
2003-03-24 3:17 ` Andrew Morton [this message]
2003-03-24 4:10 ` 2.5.65-mm4 Martin J. Bligh
2003-03-24 7:02 ` 2.5.65-mm4 Ingo Molnar
2003-03-24 7:17 ` 2.5.65-mm4 Andrew Morton
2003-03-24 7:27 ` 2.5.65-mm4 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=20030323191744.56537860.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@aracnet.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