From: Mike Galbraith <efault@gmx.de>
To: Timothy Miller <miller@techsource.com>
Cc: Con Kolivas <kernel@kolivas.org>, gaxt <gaxt@rogers.com>,
linux-kernel@vger.kernel.org
Subject: Re: WINE + Galciv + 2.6.0-test3-mm1-O15
Date: Tue, 12 Aug 2003 20:48:17 +0200 [thread overview]
Message-ID: <5.2.1.1.2.20030812203720.01a06b08@pop.gmx.net> (raw)
In-Reply-To: <3F39358D.5040506@techsource.com>
At 02:44 PM 8/12/2003 -0400, Timothy Miller wrote:
>Mike Galbraith wrote:
>
>>That sounds suspiciously similar to my scenario, but mine requires a
>>third element to trigger.
>><scritch scritch scritch>
>>What about this? In both your senario and mine, X is running low on cash
>>while doing work at the request of a client right? Charge for it.
>>If X is lower on cash than the guy he's working for, pick the client's
>>pocket... take the remainder of your slice from his sleep_avg for your
>>trouble. If you're not in_interrupt(), nothing's free. Similar to
>>Robinhood, but you take from the rich, and keep it :) He's probably
>>going straight to the bank after he wakes you anyway, so he likely won't
>>even miss it. Instead of backboost of overflow, which can cause nasty
>>problems, you could try backtheft.
>
>
>How is this different from back-boost?
With backboost, you take everything that overflows MAX_SLEEP_AVG and give
it all to the waker... you always pull-up. With back-theft (blech;),
there's constant pull-up and push-down for all parties instead of only
those who reach MAX_SLEEP_AVG, so while you'll still tend to group tasks
which are related (the original goal of backboost), it shouldn't (wild
theory) go raging out of control.
-Mike
next prev parent reply other threads:[~2003-08-12 18:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-26 21:49 WINE + Galciv + Con Kolivar's 09 patch to 2.6.0-test1-mm2 gaxt
2003-07-27 2:05 ` Con Kolivas
2003-07-28 5:17 ` 260test2+O10int breaks : " gaxt
2003-07-28 21:40 ` gaxt
2003-07-28 21:39 ` Con Kolivas
2003-07-29 2:30 ` gaxt
2003-07-29 3:25 ` Con Kolivas
2003-07-29 12:48 ` WINE + Galciv + Con Kolivas's 011 patch to 2.6.0-test2 gaxt
2003-07-29 12:46 ` Con Kolivas
2003-07-29 20:59 ` gaxt
2003-07-29 21:09 ` gaxt
2003-07-29 21:13 ` gaxt
2003-08-08 20:04 ` 2.6.0-test2-mm5 + July Wine + Galciv gaxt
2003-08-12 14:42 ` WINE + Galciv + 2.6.0-test3-mm1-O15 gaxt
2003-08-12 14:40 ` Con Kolivas
2003-08-12 18:24 ` Mike Galbraith
2003-08-12 18:44 ` Timothy Miller
2003-08-12 18:48 ` Mike Galbraith [this message]
2003-08-13 3:34 ` Con Kolivas
2003-08-13 12:47 ` Mike Galbraith
2003-08-12 15:23 Voluspa
2003-08-12 21:15 ` Con Kolivas
2003-08-13 0:54 ` Voluspa
2003-08-13 18:45 ` Timothy Miller
2003-08-13 21:21 ` 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=5.2.1.1.2.20030812203720.01a06b08@pop.gmx.net \
--to=efault@gmx.de \
--cc=gaxt@rogers.com \
--cc=kernel@kolivas.org \
--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).