From: Thomas Gleixner <tglx@linutronix.de>
To: Esben Nielsen <simlo@phys.au.dk>
Cc: linux-kernel@vger.kernel.org,
Inaky Perez-Gonzalez <inaky.perez-gonzalez@intel.com>,
Daniel Walker <dwalker@mvista.com>, Ingo Molnar <mingo@elte.hu>,
Oleg Nesterov <oleg@tv-sign.ru>
Subject: Re: patch] Real-Time Preemption, plist fixes
Date: Sun, 05 Jun 2005 10:05:06 +0200 [thread overview]
Message-ID: <1117958706.20785.243.camel@tglx.tec.linutronix.de> (raw)
In-Reply-To: <Pine.OSF.4.05.10506050953040.4252-100000@da410.phys.au.dk>
On Sun, 2005-06-05 at 09:58 +0200, Esben Nielsen wrote:
> On Sun, 5 Jun 2005, Thomas Gleixner wrote:
>
> > [...]
> > *
> > * Based on simple lists (include/linux/list.h).
> > @@ -17,35 +22,50 @@
> > * a priority too (the highest of all the nodes), stored in the head
> > * of the list (that is a node itself).
> > *
> > - * Addition is O(1), removal is O(1), change of priority of a node is
> > - * O(1).
> > + * Addition is O(N), removal is O(1), change of priority of a node is
> > + * O(N).
> > *
> > - * Addition and change of priority's order is really O(K), where K is
> > - * a constant being the maximum number of different priorities you
> > - * will store in the list. Being a constant, it means it is O(1).
> > - *
>
> What is N? The number of nodes in the list or the number of different
> priorities? If it is the number of nodes in total this exercise is
> worthless: You could just as well have a sorted list.
>
> But I hope and also think that the original explanation was correct.
Sorry, I meant K the number of different priorities.
I just find it completely bogus, that O(K) == O(1) for any K != 1.
tglx
next prev parent reply other threads:[~2005-06-05 8:04 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 [this message]
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
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=1117958706.20785.243.camel@tglx.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=dwalker@mvista.com \
--cc=inaky.perez-gonzalez@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@tv-sign.ru \
--cc=simlo@phys.au.dk \
/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®