From: Radoslaw Szkodzinski <astralstorm@gorzow.mm.pl>
To: Con Kolivas <kernel@kolivas.org>
Cc: ck@vds.kolivas.org,
"André Goddard Rosa" <andre.goddard@gmail.com>,
"linux list" <linux-kernel@vger.kernel.org>
Subject: Re: [ck] [benchmark] Interbench 2.6.16-ck/mm
Date: Sat, 25 Mar 2006 09:46:38 +0100 [thread overview]
Message-ID: <200603250946.42867.astralstorm@gorzow.mm.pl> (raw)
In-Reply-To: <200603251928.39190.kernel@kolivas.org>
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
On Saturday 25 March 2006 09:28, Con Kolivas wrote yet:
> On Saturday 25 March 2006 19:21, Radoslaw Szkodzinski wrote:
> > On Saturday 25 March 2006 05:01, Con Kolivas wrote yet:
> > > I don't expect that staircase will be better in every single situation.
> > > However it will be better more often, especially when it counts (like
> > > audio or video skipping) and far more predictable. All that in 300
> > > lines less code :)
> >
> > I thinks the main difference is those other scheduler improvements.
> > Some of them are compatible with staircase.
> > Could you also try a mixed and matched 2.6.16-ck1+mm?
>
> You're kidding, right? Check the code.
Yes and no. I was kidding about "scheduler improvements" part.
(they're mostly NUMA-only)
But of course memload, read and write latencies aren't necessarily caused by
scheduler itself.
(burn also reads a file)
The easiest thing to do would be to add staircase to -mm and see what happens.
It shouldn't be hard to port. (in fact, it may apply cleanly)
--
GPG Key id: 0xD1F10BA2
Fingerprint: 96E2 304A B9C4 949A 10A0 9105 9543 0453 D1F1 0BA2
AstralStorm
[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2006-03-25 8:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-25 2:51 Con Kolivas
2006-03-25 3:19 ` [ck] " André Goddard Rosa
2006-03-25 4:01 ` Con Kolivas
2006-03-25 8:21 ` Radoslaw Szkodzinski
2006-03-25 8:28 ` Con Kolivas
2006-03-25 8:46 ` Radoslaw Szkodzinski [this message]
2006-03-25 9:15 ` Con Kolivas
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=200603250946.42867.astralstorm@gorzow.mm.pl \
--to=astralstorm@gorzow.mm.pl \
--cc=andre.goddard@gmail.com \
--cc=ck@vds.kolivas.org \
--cc=kernel@kolivas.org \
--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 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®