mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: Mon, 6 Jun 2005 09:32:29 +0200	[thread overview]
Message-ID: <20050606073229.GA9143@elte.hu> (raw)
In-Reply-To: <Pine.OSF.4.05.10506051044340.4252-100000@da410.phys.au.dk>


* Esben Nielsen <simlo@phys.au.dk> wrote:

> Sorted lists works deterministicly O(1) on UP if no owner of the lock 
> blocks while having the lock. On SMP or worse if an owner blocks in 
> the lock, the wait list can grow very long. Thus insertion of new 
> elements takes a long time - with preemption disabled :-(

the wait list can grow only as long as the max # of RT tasks is. Sorted 
lists become 'O(1)' if we added some code that globally limits the 
number of RT tasks to say 50. E.g. /proc/sys/kernel/max_nr_RT_tasks. A 
user can override it if he needs more RT tasks. There can be an 
arbitrary number of SCHED_OTHER tasks.

(note that on Linux there is a RAM-dependent 'max # of tasks' ulimit 
which is never 'infinity', so theoretically the sorted lists are "O(1)" 
too. But this is nitpicking.)

> If this is supposed to be used for user-space PI as well I would say 
> it would have to be completely bounded, i.e. plists are certainly 
> needed. [...]

yes, it's supposed to be used for user-space PI too. What do you mean by 
'completely bounded'. Do you consider the current worst-case O(100) 
property of plists a 'completely bounded' solution?

i dont think fusyn's should be made available to non-RT tasks. If this 
restriction is preserved then fusyn's would become O(max_nr_RT_tasks) 
too.

	Ingo

  parent reply	other threads:[~2005-06-06  7:33 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-05  0:17 patch] " 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
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 [this message]
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
2005-06-06  7:44 Perez-Gonzalez, Inaky
2005-06-06  7:57 ` Ingo Molnar
2005-06-06 14:56   ` 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=20050606073229.GA9143@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®