From: Jens Axboe <axboe@suse.de>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: Con Kolivas <kernel@kolivas.org>, Andrew Morton <akpm@digeo.com>,
linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [BENCHMARK] 2.5.66-mm2 with contest
Date: Wed, 2 Apr 2003 09:58:22 +0200 [thread overview]
Message-ID: <20030402075822.GB2925@suse.de> (raw)
In-Reply-To: <3E8A97D6.3000603@cyberone.com.au>
On Wed, Apr 02 2003, Nick Piggin wrote:
> Jens Axboe wrote:
>
> >On Wed, Apr 02 2003, Nick Piggin wrote:
> >
> >>Con Kolivas wrote:
> >>
> >>
> >>>Big rise in ctar_load and io_load. Drop in read_load.
> >>>(All uniprocessor with IDE and AS elevator). AS tweaks? No obvious
> >>>scheduler tweak result changes.
> >>>
> >>>
> >>Thanks Con,
> >>I'm a bit busy now, but next week I'll work something out for it.
> >>It is most likely to be as-queue_notready-cleanup.patch. I'll
> >>wait until after Jens ports his dynamic requests stuff over to
> >>mm before I go further.
> >>
> >
> >It is ported, I sent Andrew the patch yesterday. I'm attaching it here
> >as well.
> >
> Thanks for doing that, Jens. Any CPU measurements on the hash
> goodness that you did for deadline?
Nope none yet, in fact Andrew's profile numbers show very little time
spent inside the io scheduler hash as it is. It feels like the right
thing to do though, even if the hash doesn't eat that much time.
--
Jens Axboe
next prev parent reply other threads:[~2003-04-02 7:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-02 3:23 Con Kolivas
2003-04-02 4:08 ` Nick Piggin
2003-04-02 7:42 ` Jens Axboe
2003-04-02 7:57 ` Nick Piggin
2003-04-02 7:58 ` Jens Axboe [this message]
2003-04-02 8:08 ` Nick Piggin
2003-04-02 8:15 ` Jens Axboe
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=20030402075822.GB2925@suse.de \
--to=axboe@suse.de \
--cc=akpm@digeo.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
/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
all inboxes | Powered by JetHome®