From: Davide Libenzi <davidel@xmailserver.org>
To: Con Kolivas <kernel@kolivas.org>
Cc: Szonyi Calin <sony@etc.utt.ro>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] O3int interactivity for 2.5.74-mm2
Date: Tue, 8 Jul 2003 13:55:55 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.55.0307081347310.4792@bigblue.dev.mcafeelabs.com> (raw)
In-Reply-To: <200307090654.17408.kernel@kolivas.org>
On Wed, 9 Jul 2003, Con Kolivas wrote:
> > the ratio between timeslices. If you have three processes running with
> > timeslices :
> >
> > A = 400
> > B = 200
> > C = 100
> >
> > the interactivity is the same of the one if you have :
> >
> > A = 100
> > B = 50
> > C = 25
> >
> > What changes is the maxiomum CPU blackout time that each task has to see
> > before re-emerging again from the expired array. In the first case in
> > "only" 700ms while in the first case is 175ms.
>
> and what happens to the throughput?
Nothing. You'll have more context switches in average but if you think
that the context switch time will be diluted in tenths on ms runs you'll
get nothing. I really don't like to talk w/out being backed up by numbers
but currently I am really overbooked with other tasks and I cannot follow
up this (even if I'd like to). I am currently working 12-14 hours/day on
average, and I am one of those unperfect machines that still needs 6-7
hours rest somewhere during the day :)
(but I'll do it later if Ingo does not return from Mars or if someone else
does not do it)
- Davide
next prev parent reply other threads:[~2003-07-08 20:48 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-06 17:16 Con Kolivas
2003-07-06 18:36 ` Felipe Alfaro Solana
2003-07-06 21:14 ` Con Kolivas
2003-07-06 21:17 ` Con Kolivas
2003-07-07 3:19 ` Con Kolivas
2003-07-07 9:13 ` Felipe Alfaro Solana
2003-07-07 9:40 ` Mike Galbraith
2003-07-07 10:25 ` Con Kolivas
2003-07-07 14:06 ` Mike Galbraith
2003-07-07 14:10 ` Con Kolivas
2003-07-07 10:51 ` Nick Sanders
2003-07-07 12:19 ` Marc-Christian Petersen
2003-07-07 13:14 ` Con Kolivas
2003-07-08 0:31 ` Zwane Mwaikambo
2003-07-09 10:12 ` Marc-Christian Petersen
2003-07-09 10:13 ` Marc-Christian Petersen
2003-07-09 10:22 ` Con Kolivas
2003-07-09 10:23 ` Marc-Christian Petersen
2003-07-09 10:37 ` Con Kolivas
2003-07-09 10:40 ` Marc-Christian Petersen
2003-07-07 13:25 ` Helge Hafting
2003-07-08 6:35 ` Alex Riesen
2003-07-08 7:11 ` Szonyi Calin
2003-07-08 7:46 ` Davide Libenzi
2003-07-08 7:59 ` Con Kolivas
2003-07-08 15:12 ` Davide Libenzi
2003-07-08 20:54 ` Con Kolivas
2003-07-08 20:55 ` Davide Libenzi [this message]
2003-07-08 8:03 ` Con Kolivas
2003-07-10 16:27 ` Szonyi Calin
2003-07-09 15:08 Luis Miguel Garcia
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=Pine.LNX.4.55.0307081347310.4792@bigblue.dev.mcafeelabs.com \
--to=davidel@xmailserver.org \
--cc=akpm@osdl.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sony@etc.utt.ro \
/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®