From: Jens Axboe <axboe@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Scott L. Burson" <gyro@zeta-soft.com>, linux-kernel@vger.kernel.org
Subject: Re: Performance issue on dual Athlon MP
Date: Mon, 11 Mar 2002 10:32:17 +0100 [thread overview]
Message-ID: <20020311093217.GB31108@suse.de> (raw)
In-Reply-To: <15494.32860.773969.762627@kali.zeta-soft.com> <E16j7Yh-0004CL-00@the-village.bc.nu>
In-Reply-To: <E16j7Yh-0004CL-00@the-village.bc.nu>
On Thu, Mar 07 2002, Alan Cox wrote:
> > BTW, this doesn't seem like a preemption issue, considering that throughput
> > is very definitely affected as well as latency.
> >
> > Anyway, please let me know if there's anything I can do, within my
> > constraints, to help. (As you can guess, though, I don't have any kernel
> > debugging experience.)
>
> It sounds like the hit you are taking is from highmem and I/O (having to
> copy pages lower into memory so the I/O subsystem can use them). Some of
> that is in the hard to fix for 2.4 category with the x86. There are some
> experimental patches around but they are experimental.
If you are referring to my block-highmem patch, then it's not considered
too experiemental anymore. It's been a long time since any problems have
been reported.
Scott, a small profile run would give us the information needed to tell
whether this is a bounce problem or not. Boot the kernel with profile=2,
then do a readprofile -r ; run problematic stuff ; readprofile >
prof_data
and share the prof_data.
--
Jens Axboe
next prev parent reply other threads:[~2002-03-11 9:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-06 19:28 Performance issue on dual Athlon MP Dieter Nützel
2002-03-06 20:49 ` John Jasen
2002-03-07 23:20 ` Scott L. Burson
2002-03-07 23:44 ` Alan Cox
2002-03-08 0:24 ` Randy.Dunlap
2002-03-11 9:32 ` Jens Axboe [this message]
2002-03-11 20:13 ` Randy.Dunlap
2002-03-14 15:49 ` Scott L. Burson
-- strict thread matches above, loose matches on Subject: below --
2002-03-06 22:09 rwhron
2002-03-06 18:47 Scott L. Burson
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=20020311093217.GB31108@suse.de \
--to=axboe@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gyro@zeta-soft.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.