From: Xavier Bestel <xavier.bestel@free.fr>
To: Ingo Molnar <mingo@elte.hu>
Cc: jvlists@ntlworld.com, Linus Torvalds <torvalds@transmeta.com>,
Jeff Garzik <jgarzik@pobox.com>, Andrew Morton <akpm@digeo.com>,
rml@tech9.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] "HT scheduler", sched-2.5.63-B3
Date: 07 Mar 2003 09:15:44 +0100 [thread overview]
Message-ID: <1047024942.25382.12.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.44.0303061925050.17038-100000@localhost.localdomain>
Le jeu 06/03/2003 à 19:27, Ingo Molnar a écrit:
> On Thu, 6 Mar 2003 jvlists@ntlworld.com wrote:
>
> > P.S. IMVHO the xine problem is completely different as has nothing to
> > with interactivity but with the fact that it is soft real-time. i.e. you
> > need to distingish xine from say a gimp filter or a 3D renderer with
> > incremental live updates of the scene it is creating.
>
> it is the same category of problems: xine and X are both applications,
> which, if lagged, are noticed by users.
Actually I don't think so:
- X and games need hard interactivity: they have to compute fast a
response to an input.
- xine can precompute a few frames if it wants (I dunno if it does) and
just needs a precise timing to display them and sync the audio buffers.
It could do with CPU slices if X does the right 'display this frame at
this time' thing.
Xav
next prev parent reply other threads:[~2003-03-07 8:04 UTC|newest]
Thread overview: 100+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-28 9:50 [patch] "HT scheduler", sched-2.5.63-B3 Ingo Molnar
2003-02-28 21:12 ` Andrew Morton
2003-02-28 21:23 ` Robert Love
2003-03-01 4:25 ` Andrew Morton
2003-03-06 3:20 ` Linus Torvalds
2003-03-06 7:45 ` Andrew Morton
2003-03-06 7:47 ` Ingo Molnar
2003-03-06 15:07 ` Linus Torvalds
2003-03-06 16:54 ` Ingo Molnar
2003-03-06 17:03 ` Linus Torvalds
2003-03-06 17:24 ` Ingo Molnar
2003-03-06 17:42 ` Linus Torvalds
2003-03-06 17:54 ` Ingo Molnar
2003-03-06 18:02 ` Linus Torvalds
2003-03-06 18:11 ` Ingo Molnar
2003-03-06 17:55 ` John Levon
2003-03-06 18:07 ` Linus Torvalds
2003-03-06 18:11 ` John Levon
2003-03-06 18:16 ` Linus Torvalds
2003-03-06 18:15 ` Ingo Molnar
2003-03-06 18:20 ` Linus Torvalds
2003-03-06 18:10 ` David S. Miller
2003-03-06 18:18 ` Ingo Molnar
2003-03-07 5:57 ` Ingo Molnar
2003-03-07 5:54 ` Shawn
2003-03-07 6:04 ` Ingo Molnar
2003-03-07 14:28 ` jlnance
2003-03-07 6:45 ` Aaron Lehmann
2003-03-07 6:50 ` Ingo Molnar
2003-03-07 7:00 ` Aaron Lehmann
2003-03-07 7:36 ` Ingo Molnar
2003-03-08 18:28 ` Aaron Lehmann
2003-03-07 7:00 ` Andrew Morton
2003-03-07 3:19 ` Horst von Brand
2003-03-06 15:37 ` Linus Torvalds
2003-03-06 16:01 ` Jeff Garzik
2003-03-06 16:51 ` Linus Torvalds
2003-03-06 17:11 ` Ingo Molnar
2003-03-06 17:52 ` jvlists
2003-03-06 18:27 ` Ingo Molnar
2003-03-07 8:15 ` Xavier Bestel [this message]
2003-03-06 23:18 ` Robert Love
2003-03-06 18:49 ` Alan Cox
2003-03-06 17:55 ` Linus Torvalds
2003-03-06 18:04 ` Ingo Molnar
2003-03-06 18:13 ` Martin J. Bligh
2003-03-06 18:26 ` Linus Torvalds
2003-03-08 0:05 ` Daniel Phillips
2003-03-06 17:58 ` Ingo Molnar
2003-03-06 17:17 ` Ingo Molnar
2003-03-06 18:06 ` Dimitrie O. Paun
2003-03-06 22:14 ` Martin J. Bligh
2003-03-06 22:31 ` Dimitrie O. Paun
2003-03-06 23:05 ` Robert Love
2003-03-06 23:33 ` Martin J. Bligh
2003-03-06 18:25 ` Alan Cox
2003-03-06 17:35 ` Linus Torvalds
2003-03-06 22:30 ` Eric Northup
2003-03-06 23:40 ` Martin J. Bligh
2003-03-07 0:02 ` Linus Torvalds
2003-03-07 0:09 ` Dimitrie O. Paun
2003-03-06 22:00 ` Bill Davidsen
2003-03-06 17:13 ` Ingo Molnar
2003-03-06 17:30 ` Linus Torvalds
2003-03-06 17:33 ` Ingo Molnar
2003-03-06 17:50 ` Ingo Molnar
2003-03-06 18:00 ` Linus Torvalds
2003-03-06 20:42 ` Andrew Morton
2003-03-06 22:18 ` Robert Love
2003-03-07 5:52 ` Ingo Molnar
2003-03-07 5:51 ` Shawn
2003-03-07 6:01 ` Ingo Molnar
2003-03-07 6:07 ` Andrew Morton
2003-03-07 6:15 ` Ingo Molnar
2003-03-07 10:19 ` Helge Hafting
2003-03-07 11:06 ` Ingo Molnar
2003-03-07 7:45 ` Mike Galbraith
2003-03-07 7:45 ` Ingo Molnar
[not found] ` <Pine.LNX.4.44.0303070842420.4572-100000@localhost.localdom ain>
2003-03-07 8:09 ` Mike Galbraith
2003-03-07 8:10 ` Andrew Morton
2003-03-07 8:26 ` Mike Galbraith
2003-03-07 8:15 ` Ingo Molnar
[not found] ` <Pine.LNX.4.44.0303070913370.5173-100000@localhost.localdom ain>
2003-03-07 8:34 ` Mike Galbraith
2003-03-07 8:31 ` Ingo Molnar
2003-03-06 22:03 ` Martin Waitz
2003-03-06 22:07 ` Robert Love
2003-03-06 22:35 ` Martin Waitz
2003-03-06 22:56 ` Robert Love
2003-03-06 23:27 ` Martin Waitz
2003-03-06 23:36 ` Robert Love
2003-03-07 10:39 ` Ingo Molnar
2003-03-07 10:27 ` Ingo Molnar
2003-03-06 6:58 ` [patch] "interactivity changes", sched-2.5.64-A4 Ingo Molnar
2003-03-06 10:00 ` Andrew Morton
2003-03-06 10:07 ` [patch] "interactivity changes", sched-2.5.64-A5 Ingo Molnar
2003-03-06 10:16 ` [patch] "HT scheduler", sched-2.5.63-B3 Chris Wedgwood
2003-03-06 10:18 ` Ingo Molnar
[not found] <5.2.0.9.2.20030307093435.01a8fe88@pop.gmx.net>
2003-03-07 9:30 ` Ingo Molnar
[not found] ` <Pine.LNX.4.44.0303071003060.6318-100000@localhost.localdom ain>
2003-03-07 9:38 ` Mike Galbraith
-- strict thread matches above, loose matches on Subject: below --
2003-03-10 19:53 Perez-Gonzalez, Inaky
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=1047024942.25382.12.camel@localhost \
--to=xavier.bestel@free.fr \
--cc=akpm@digeo.com \
--cc=jgarzik@pobox.com \
--cc=jvlists@ntlworld.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rml@tech9.net \
--cc=torvalds@transmeta.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.