From: Oleg Nesterov <oleg@tv-sign.ru>
To: Daniel Walker <dwalker@mvista.com>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Inaky Perez-Gonzalez <inaky.perez-gonzalez@intel.com>
Subject: Re: [patch] Real-Time Preemption, -RT-2.6.12-rc4-V0.7.47-06
Date: Wed, 01 Jun 2005 19:47:23 +0400 [thread overview]
Message-ID: <429DD88B.7168BC77@tv-sign.ru> (raw)
In-Reply-To: Pine.LNX.4.44.0506010756490.23057-100000@dhcp153.mvista.com
Daniel Walker wrote:
>
> On Wed, 1 Jun 2005, Oleg Nesterov wrote:
>
> > Sorry, I don't understand you. Could you please explain this to me?
>
> plist_for_each() was just created to walk through all the nodes in the
> list, There is no guaranteed ordering via that method. From your test it
> appeared to be working since you printed all the nodes you inserted.
Yes, plist_for_each() without plist_entry() works.
> There are other methods like plist_first() which will give you FIFO
> ordered nodes (or should) . The reason is that plist_first() pulls off the
> dp_node , which is the first node inserted at that priority. All the other
> nodes are inserted behind the dp_node. That's why I used list_add() and
> not list_add_tail()
So plist_for_each() works in reverse order, and the comment about
fifo ordering applies only to plist_first(). Thanks for explanation.
I don't understand why you are doing it this way, though.
Oleg.
next prev parent reply other threads:[~2005-06-01 15:41 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-23 15:05 [patch] Real-Time Preemption, -RT-2.6.12-rc4-V0.7.47-06 Oleg Nesterov
2005-05-23 15:12 ` Daniel Walker
2005-05-23 15:53 ` Oleg Nesterov
2005-05-23 16:48 ` Oleg Nesterov
2005-06-01 9:21 ` Ingo Molnar
2005-06-01 13:04 ` Daniel Walker
2005-06-01 13:11 ` Ingo Molnar
2005-06-01 13:21 ` Daniel Walker
2005-06-01 14:43 ` Oleg Nesterov
2005-06-01 14:43 ` Daniel Walker
2005-06-01 15:02 ` Oleg Nesterov
2005-06-01 15:05 ` Daniel Walker
2005-06-01 15:47 ` Oleg Nesterov [this message]
2005-06-01 15:43 ` Daniel Walker
-- strict thread matches above, loose matches on Subject: below --
2005-05-24 1:47 Perez-Gonzalez, Inaky
2005-05-23 8:26 Ingo Molnar
2005-05-23 9:34 ` Serge Noiraud
2005-05-23 11:23 ` Ingo Molnar
2005-05-23 14:30 ` K.R. Foley
2005-05-24 16:38 ` K.R. Foley
2005-05-25 11:34 ` Ingo Molnar
2005-05-25 11:35 ` Ingo Molnar
2005-05-25 13:28 ` K.R. Foley
2005-05-25 14:03 ` Ingo Molnar
2005-05-25 14:18 ` K.R. Foley
2005-05-25 15:20 ` K.R. Foley
2005-05-26 7:45 ` Ingo Molnar
2005-05-26 10:53 ` K.R. Foley
2005-05-26 15:23 ` K.R. Foley
2005-05-25 20:38 ` Michal Schmidt
2005-05-27 20:46 ` Michal Schmidt
2005-05-28 5:53 ` Ingo Molnar
2005-05-30 9:51 ` Michal Schmidt
2005-05-30 14:38 ` Ingo Molnar
2005-05-30 14:50 ` Ingo Molnar
2005-05-30 16:47 ` Michal Schmidt
2005-05-30 18:09 ` Ingo Molnar
2005-06-01 17:28 ` Esben Nielsen
2005-06-01 9:19 ` Ingo Molnar
2005-06-01 9:32 ` Michal Schmidt
2005-06-01 9:39 ` Ingo Molnar
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=429DD88B.7168BC77@tv-sign.ru \
--to=oleg@tv-sign.ru \
--cc=dwalker@mvista.com \
--cc=inaky.perez-gonzalez@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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