From: Jens Axboe <axboe@suse.de>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Mikael Pettersson <mikpe@csd.uu.se>,
lkml <linux-kernel@vger.kernel.org>,
mjh@vr-web.de, Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [patch] 2.5.2 scheduler code for 2.4.18-pre1 ( was 2.5.2-pre performance degradation on an old 486 )
Date: Mon, 7 Jan 2002 08:33:31 +0100 [thread overview]
Message-ID: <20020107083331.C1755@suse.de> (raw)
In-Reply-To: <200201070133.CAA03628@harpo.it.uu.se> <Pine.LNX.4.40.0201061836030.1000-100000@blue1.dev.mcafeelabs.com>
In-Reply-To: <Pine.LNX.4.40.0201061836030.1000-100000@blue1.dev.mcafeelabs.com>
On Sun, Jan 06 2002, Davide Libenzi wrote:
> On Mon, 7 Jan 2002, Mikael Pettersson wrote:
>
> > On Sun, 6 Jan 2002 15:59:05 -0800 (PST), Davide Libenzi wrote:
> > >I made this patch for Andrea and it's the scheduler code for 2.4.18-pre1
> > >Could someone give it a try on old 486s
> >
> > Done. On my '93 vintage 486, 2.4.18p1 + your scheduler results in very
> > bursty I/O and poor performance, just like I reported for 2.5.2-pre7.
>
> Can you try some changes that i'll tell you ?
Did you _try_ the ISA bounce trick to reproduce locally??
--
Jens Axboe
next prev parent reply other threads:[~2002-01-07 7:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-07 1:33 [patch] 2.5.2 scheduler code for 2.4.18-pre1 ( was 2.5.2-pre performance degradation on an old 486 ) Mikael Pettersson
2002-01-07 2:36 ` Davide Libenzi
2002-01-07 7:33 ` Jens Axboe [this message]
2002-01-07 18:12 ` Davide Libenzi
-- strict thread matches above, loose matches on Subject: below --
2002-01-06 10:21 2.5.2-pre performance degradation on an old 486 Jens Axboe
2002-01-06 23:59 ` [patch] 2.5.2 scheduler code for 2.4.18-pre1 ( was 2.5.2-pre performance degradation on an old 486 ) Davide Libenzi
2002-01-07 1:38 ` Andrea Arcangeli
2002-01-07 14:35 ` J.A. Magallon
2002-01-07 14:37 ` Andrea Arcangeli
2002-01-07 7:32 ` Jens Axboe
2002-01-07 18:10 ` Davide Libenzi
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=20020107083331.C1755@suse.de \
--to=axboe@suse.de \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
--cc=mjh@vr-web.de \
--cc=torvalds@transmeta.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