From: Nick Piggin <piggin@cyberone.com.au>
To: Mike Galbraith <efault@gmx.de>
Cc: rob@landley.net, Con Kolivas <kernel@kolivas.org>,
linux kernel mailing list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@elte.hu>,
Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
Subject: Re: [PATCH] O13int for interactivity
Date: Tue, 12 Aug 2003 17:07:13 +1000 [thread overview]
Message-ID: <3F389221.6080202@cyberone.com.au> (raw)
In-Reply-To: <5.2.1.1.2.20030812075224.01988de8@pop.gmx.net>
Mike Galbraith wrote:
> At 12:51 PM 8/12/2003 +1000, Nick Piggin wrote:
>
>
>> Rob Landley wrote:
>>
>>> On Tuesday 05 August 2003 06:32, Nick Piggin wrote:
>>>
>>>
>>>> But by employing the kernel's services in the shape of a blocking
>>>> syscall, all sleeps are intentional.
>>>
>>>
>>> Wrong. Some sleeps indicate "I have run out of stuff to do right
>>> now, I'm going to wait for a timer or another process or something
>>> to wake me up with new work".
>>>
>>>
>>>
>>> Some sleeps indicate "ideally this would run on an enormous ramdisk
>>> attached to gigabit ethernet, but hard drives and internet
>>> connections are just too slow so my true CPU-hogness is hidden by
>>> the fact I'm running on a PC instead of a mainframe."
>>
>>
>> I don't quite understand what you are getting at, but if you don't
>> want to
>> sleep you should be able to use a non blocking syscall. But in some
>> cases
>> I think there are times when you may not be able to use a non
>> blocking call.
>> And if a process is a CPU hog, its a CPU hog. If its not its not.
>> Doesn't
>> matter how it would behave on another system.
>
>
> Ah, but there is something there. Take the X and xmms's gl thread
> thingy I posted a while back. (X runs long enough to expire in the
> presence of a couple of low priority cpu hogs. gl thread, which is a
> mondo cpu hog, and normally runs and runs and runs at cpu hog
> priority, suddenly acquires extreme interactive priority, and X, which
> is normally sleepy suddenly becomes permanently runnable at cpu hog
> priority) The gl thread starts sleeping because X isn't getting
> enough cpu to be able to get it's work done and go to sleep. The gl
> thread isn't voluntarily sleeping, and X isn't voluntarily running.
> The behavior change is forced upon both.
It does... It is I tell ya!
Look, the gl thread is probably _very_ explicitly asking to sleep. No I
don't know how X works, but I have an idea that select is generally used
as an event notification, right?
Now the gl thread is essentially saying "wait until X finishes the work
I've given it, or I get some other event": ie. "put me to sleep until
this fd becomes readable".
OK maybe your scenario is a big problem. Its not due to any imagined
semantics in the way things are sleeping. Its due to the scheduler.
next prev parent reply other threads:[~2003-08-12 7:07 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 16:07 [PATCH] O13int for interactivity Con Kolivas
2003-08-04 18:24 ` Felipe Alfaro Solana
2003-08-04 19:15 ` Antonio Vargas
2003-08-04 21:32 ` Con Kolivas
2003-08-04 20:11 ` Mike Galbraith
2003-08-04 22:11 ` Con Kolivas
2003-08-05 7:10 ` Mike Galbraith
2003-08-05 2:11 ` Nick Piggin
2003-08-05 2:20 ` Con Kolivas
2003-08-05 2:21 ` Nick Piggin
2003-08-05 3:06 ` Con Kolivas
2003-08-05 3:17 ` Nick Piggin
2003-08-06 18:48 ` Interactivity improvements Timothy Miller
2003-08-06 19:01 ` Mike Fedyk
2003-08-06 20:09 ` Helge Hafting
2003-08-06 21:15 ` Con Kolivas
2003-08-05 3:18 ` [PATCH] O13int for interactivity Con Kolivas
2003-08-05 3:31 ` Nick Piggin
2003-08-05 5:04 ` Con Kolivas
2003-08-05 5:12 ` Nick Piggin
2003-08-05 5:16 ` Con Kolivas
2003-08-05 5:28 ` Nick Piggin
2003-08-05 10:22 ` Con Kolivas
2003-08-05 10:32 ` Nick Piggin
2003-08-05 10:45 ` Con Kolivas
2003-08-05 10:48 ` Nick Piggin
2003-08-05 10:56 ` Con Kolivas
2003-08-05 11:03 ` Nick Piggin
2003-08-05 11:12 ` Con Kolivas
2003-08-05 11:23 ` Nick Piggin
2003-08-05 11:34 ` Con Kolivas
2003-08-05 10:54 ` Arjan van de Ven
2003-08-05 11:10 ` Con Kolivas
2003-08-06 21:33 ` Timothy Miller
2003-08-06 21:33 ` Con Kolivas
2003-08-07 0:27 ` Timothy Miller
2003-08-07 0:27 ` Con Kolivas
2003-08-07 0:44 ` Timothy Miller
2003-08-11 6:48 ` Rob Landley
2003-08-11 15:47 ` William Lee Irwin III
2003-08-12 2:51 ` Nick Piggin
2003-08-12 6:16 ` Mike Galbraith
2003-08-12 7:07 ` Nick Piggin [this message]
2003-08-12 7:18 ` Nick Piggin
2003-08-12 9:42 ` Mike Galbraith
2003-08-12 21:11 ` Mike Fedyk
2003-08-13 6:55 ` Mike Galbraith
2003-08-12 9:22 ` Mike Galbraith
2003-08-12 9:37 ` Nick Piggin
2003-08-12 9:48 ` Mike Galbraith
2003-08-12 10:29 ` Rob Landley
2003-08-12 11:08 ` Nick Piggin
2003-08-12 11:35 ` Rob Landley
2003-08-12 11:58 ` Nick Piggin
2003-08-13 2:08 ` jw schultz
2003-08-13 3:07 ` Gene Heskett
2003-08-13 3:24 ` Nick Piggin
2003-08-13 5:24 ` Gene Heskett
2003-08-13 5:43 ` Andrew McGregor
2003-08-13 12:33 ` Gene Heskett
2003-08-14 5:03 ` Andrew McGregor
2003-08-14 10:48 ` Gene Heskett
2003-08-12 15:36 ` Timothy Miller
2003-08-05 6:03 ` Andrew Morton
2003-08-05 7:26 ` Con Kolivas
2003-08-05 8:12 ` Oliver Neukum
2003-08-05 8:20 ` Con Kolivas
2003-08-05 8:27 ` Mike Galbraith
2003-08-05 8:43 ` Con Kolivas
2003-08-05 9:09 ` Mike Galbraith
2003-08-05 9:19 ` Con Kolivas
2003-08-05 10:04 ` Nick Piggin
2003-08-11 6:57 ` Rob Landley
2003-08-11 15:58 ` William Lee Irwin III
2003-08-05 7:53 ` Mike Galbraith
[not found] <gQ4n.5oS.7@gated-at.bofh.it>
[not found] ` <jUl6.5eh.1@gated-at.bofh.it>
[not found] ` <jUuT.5kZ.15@gated-at.bofh.it>
[not found] ` <jWn1.6K1.11@gated-at.bofh.it>
2003-08-13 13:48 ` Pascal Schmidt
2003-08-13 14:50 ` Gene Heskett
-- strict thread matches above, loose matches on Subject: below --
2003-08-06 10:35 Voluspa
2003-08-04 19:12 Voluspa
2003-07-27 15:12 [PATCH] O10int " Con Kolivas
2003-07-28 18:08 ` Valdis.Kletnieks
2003-07-28 18:40 ` Andrew Morton
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
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=3F389221.6080202@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=akpm@osdl.org \
--cc=efault@gmx.de \
--cc=felipe_alfaro@linuxmail.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rob@landley.net \
/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).