From: Ingo Molnar <mingo@elte.hu>
To: Esben Nielsen <simlo@phys.au.dk>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org,
Inaky Perez-Gonzalez <inaky.perez-gonzalez@intel.com>,
Daniel Walker <dwalker@mvista.com>,
Oleg Nesterov <oleg@tv-sign.ru>
Subject: Re: patch] Real-Time Preemption, plist fixes
Date: Sun, 5 Jun 2005 10:53:13 +0200 [thread overview]
Message-ID: <20050605085313.GA30946@elte.hu> (raw)
In-Reply-To: <Pine.OSF.4.05.10506051014230.4252-100000@da410.phys.au.dk>
* Esben Nielsen <simlo@phys.au.dk> wrote:
> When K is a constant or bounded by a constant (140 in this
> application) any function which is O(K) is O(1) per definition of O!
technically you are right. But the question is - while K is considered a
constant, and N (nr_running_RT_tasks) is technically not bounded - in
practice N is bounded just as much. Have you ever seen any hard-RT
application that has more than 140 threads _running at the same time_ on
a single CPU? You can even enforce it to be theoretically bounded, via
ulimits.
in fact, K and N should be pretty close to each other for most
applications. I'd be interested in real application scenarios where N is
much (== more than 10 times) larger than K and plists really matter.
Ingo
next prev parent reply other threads:[~2005-06-05 8:55 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-05 0:17 Thomas Gleixner
2005-06-05 0:53 ` Daniel Walker
2005-06-05 2:33 ` Plist cleanup on RT Daniel Walker
2005-06-05 8:32 ` patch] Real-Time Preemption, plist fixes Thomas Gleixner
2005-06-05 10:53 ` Thomas Gleixner
2005-06-05 7:58 ` Esben Nielsen
2005-06-05 8:05 ` Thomas Gleixner
2005-06-05 8:42 ` Esben Nielsen
2005-06-05 8:53 ` Ingo Molnar [this message]
2005-06-05 9:00 ` Esben Nielsen
2005-06-05 8:18 ` Ingo Molnar
2005-06-05 8:21 ` 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=20050605085313.GA30946@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®