All of lore.kernel.org
 help / color / mirror / Atom feed
From: Haoqiang Zheng <hzheng@cs.columbia.edu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Pavel Machek <pavel@ucw.cz>, Nick Piggin <piggin@cyberone.com.au>,
	William Lee Irwin III <wli@holomorphy.com>,
	Mike Galbraith <efault@gmx.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [CFT][PATCH] new scheduler policy
Date: Mon, 08 Sep 2003 10:20:00 -0400	[thread overview]
Message-ID: <3F5C9010.1080607@cs.columbia.edu> (raw)
In-Reply-To: <1063028436.21084.30.camel@dhcp23.swansea.linux.org.uk>

How do you define "priority inversion" if the app is remote?

Alan Cox wrote:

>On Maw, 2003-09-02 at 15:25, Pavel Machek wrote:
>  
>
>>>in the best position to decide which process is more important. 
>>>That's why I proposed kernel based approach.
>>>      
>>>
>>Tasks can easily report their interactivity needs/nice value.
>>X are already depend on clients not trying to screw each other,
>>so thats okay.
>>    
>>
>
>There is a slight problem with a kernel based approach too - the app may
>be remote. 
>
>Alan
>  
>



  reply	other threads:[~2003-09-08 14:20 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-19  1:53 [CFT][PATCH] new scheduler policy Nick Piggin
2003-08-19  2:35 ` William Lee Irwin III
2003-08-19  2:46   ` Nick Piggin
2003-08-19  2:59     ` Nick Piggin
2003-08-19  5:15       ` Matt Mackall
2003-08-19  5:34         ` Nick Piggin
2003-08-19  5:45           ` Matt Mackall
2003-08-19 10:24 ` Mike Galbraith
2003-08-19 13:40   ` Nick Piggin
2003-08-19 18:49     ` Mike Galbraith
2003-08-20  2:13   ` William Lee Irwin III
2003-08-25 13:47     ` Haoqiang Zheng
2003-08-25 14:03       ` Nick Piggin
2003-08-25 15:11         ` Haoqiang Zheng
2003-09-02 14:25           ` Pavel Machek
2003-09-08 13:40             ` Alan Cox
2003-09-08 14:20               ` Haoqiang Zheng [this message]
2003-09-08 14:28                 ` Alan Cox
2003-09-08 15:10                   ` Haoqiang Zheng
2003-08-22  8:55 ` Roger Luethi
2003-08-22 13:08   ` Nick Piggin
2003-08-22 15:11     ` Roger Luethi
2003-08-23  0:22       ` Nick Piggin

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=3F5C9010.1080607@cs.columbia.edu \
    --to=hzheng@cs.columbia.edu \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=piggin@cyberone.com.au \
    --cc=wli@holomorphy.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.