From: Ingo Molnar <mingo@elte.hu>
To: "Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>
Cc: Esben Nielsen <simlo@phys.au.dk>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, Daniel Walker <dwalker@mvista.com>,
Oleg Nesterov <oleg@tv-sign.ru>
Subject: Re: [patch] Real-Time Preemption, plist fixes
Date: Mon, 6 Jun 2005 09:57:28 +0200 [thread overview]
Message-ID: <20050606075728.GA13088@elte.hu> (raw)
In-Reply-To: <F989B1573A3A644BAB3920FBECA4D25A037001B3@orsmsx407>
* Perez-Gonzalez, Inaky <inaky.perez-gonzalez@intel.com> wrote:
> >From: Ingo Molnar [mailto:mingo@elte.hu]
> >
> >so the question is - can we have an extreme (larger than 140) number of
> >RT tasks? If yes, why are they all RT - they can have no expectation of
> >good latencies with a possible load factor of 140!
>
> In practice, didn't we want most tasks to behave like RT? (for
> interactivity purposes) -- I recall hearing that's basically what good
> interactivity meant; short reponse times to events.
that's not what the current code does (and it's not what the non-plist
code did either). We dont do PI handling for non-RT tasks. They
basically have no RT expectations at all, and including them in the PI
mechanism would only slow them down, and would increase the latencies of
the RT tasks as well.
But indeed it could improve interactivity (but this has not been proven
yet) - and also for testing purposes it would sure be useful, so we
should perhaps make ALL_TASKS_PI default-on, as Daniel suggests. If that
is done then plists are indeed a superior solution. But if in the end we
decide to only include RT tasks in the PI mechanism (which could easily
happen) then there seems to be little practical difference between
sorted lists and plists.
Ingo
next prev parent reply other threads:[~2005-06-06 7:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 7:44 [patch] Real-Time Preemption, plist fixes Perez-Gonzalez, Inaky
2005-06-06 7:57 ` Ingo Molnar [this message]
2005-06-06 14:56 ` Daniel Walker
-- strict thread matches above, loose matches on Subject: below --
2005-06-05 0:17 patch] " Thomas Gleixner
2005-06-05 8:26 ` [patch] " Ingo Molnar
2005-06-05 8:53 ` Thomas Gleixner
2005-06-05 9:47 ` Ingo Molnar
2005-06-05 15:08 ` Daniel Walker
2005-06-05 8:54 ` Esben Nielsen
2005-06-05 13:49 ` Ingo Molnar
2005-06-05 14:35 ` Esben Nielsen
2005-06-06 7:32 ` Ingo Molnar
2005-06-06 8:57 ` Esben Nielsen
2005-06-06 12:08 ` Ingo Molnar
2005-06-06 15:04 ` Daniel Walker
2005-06-05 14:51 ` Daniel Walker
2005-06-05 15:17 ` Thomas Gleixner
2005-06-05 15:21 ` Daniel Walker
2005-06-05 15:02 ` Daniel Walker
2005-06-05 16:29 ` Daniel Walker
2005-06-06 7:44 ` Ingo Molnar
2005-06-06 14:49 ` Daniel Walker
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=20050606075728.GA13088@elte.hu \
--to=mingo@elte.hu \
--cc=dwalker@mvista.com \
--cc=inaky.perez-gonzalez@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
--cc=simlo@phys.au.dk \
--cc=tglx@linutronix.de \
/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.