From: Con Kolivas <kernel@kolivas.org>
To: "Diego Calleja García" <diegocg@teleline.es>
Cc: miller@techsource.com, linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] O10int for interactivity
Date: Wed, 30 Jul 2003 11:36:06 +1000 [thread overview]
Message-ID: <200307301136.06396.kernel@kolivas.org> (raw)
In-Reply-To: <20030730031616.3ed14362.diegocg@teleline.es>
On Wed, 30 Jul 2003 11:16, Diego Calleja García wrote:
> El Wed, 30 Jul 2003 00:35:01 +1000 Con Kolivas <kernel@kolivas.org>
escribió:
> > That's not as silly as it sounds. In fact it should be dead easy to
> > increase/decrease the amount of anticipatory time based on the bonus from
> > looking at the code. I dunno how the higher filesystem gods feel about
> > this though.
>
> I've done a small patch (one line) which tries to implement that.
> At as-iosched.c:as_add_request() there's:
The logic is in the difference between the dynamic and the static priority to
determine if a task is interactive.
current->static_prio - current->prio
will give you a number of -5 to +5, with +5 being a good bonus and vice versa.
however you need to ensure that the value you are fiddling with in the i/o
scheduler is actually due to the current process[1]
On top of that, the p->prio itself will give you a number of 0-140 depending
with higher being a lower priority task; numbers 100-140 are for user tasks
and <100 for real time tasks.
These all change if you fiddle with the magic in bonus ratios and max rt prio
etc.
Con
[1] This is why I didn't bother posting my attempts ;)
next prev parent reply other threads:[~2003-07-30 1:31 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-27 15:12 [PATCH] O10int for interactivity Con Kolivas
2003-07-27 16:26 ` Wade
2003-07-27 19:15 ` Felipe Alfaro Solana
2003-07-28 7:51 ` Wiktor Wodecki
2003-07-28 7:55 ` Andrew Morton
2003-07-28 8:00 ` Wiktor Wodecki
2003-07-28 17:12 ` Jose Luis Domingo Lopez
2003-07-28 18:08 ` Valdis.Kletnieks
2003-07-28 18:40 ` Andrew Morton
2003-07-28 21:29 ` Wiktor Wodecki
2003-07-28 21:35 ` Andrew Morton
2003-07-31 6:36 ` Nick Piggin
2003-07-31 7:43 ` Con Kolivas
2003-07-31 7:58 ` Nick Piggin
2003-07-31 14:59 ` Jamie Lokier
2003-07-31 15:24 ` Oliver Neukum
2003-07-31 15:40 ` Jamie Lokier
2003-07-31 22:56 ` Nick Piggin
2003-08-04 18:51 ` [PATCH] O13int " Felipe Alfaro Solana
2003-08-04 18:58 ` Felipe Alfaro Solana
2003-08-04 21:46 ` Con Kolivas
2003-08-04 22:16 ` Felipe Alfaro Solana
2003-07-29 14:21 ` [PATCH] O10int " Timothy Miller
2003-07-29 14:35 ` Con Kolivas
2003-07-29 15:35 ` Timothy Miller
2003-07-30 1:16 ` Diego Calleja García
2003-07-30 1:36 ` Con Kolivas [this message]
2003-07-30 19:28 ` aradorlinux
2003-07-30 19:34 ` Andrew Morton
2003-07-29 15:28 ` Valdis.Kletnieks
2003-07-29 15:44 ` Timothy Miller
2003-07-29 15:45 ` Valdis.Kletnieks
2003-07-27 19:50 Voluspa
2003-07-28 2:05 Voluspa
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=200307301136.06396.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=akpm@osdl.org \
--cc=diegocg@teleline.es \
--cc=linux-kernel@vger.kernel.org \
--cc=miller@techsource.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;
as well as URLs for NNTP newsgroup(s).