From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Daniel Walker <dwalker@mvista.com>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Gregory Haskins <ghaskins@novell.com>,
Oleg Nesterov <oleg@tv-sign.ru>
Subject: Re: [RFC/PATCH 3/5] rt: plist_head_splice
Date: Tue, 23 Oct 2007 18:26:33 +0200 [thread overview]
Message-ID: <1193156793.6914.0.camel@twins> (raw)
In-Reply-To: <Pine.LNX.4.58.0710231108050.31159@gandalf.stny.rr.com>
[-- Attachment #1: Type: text/plain, Size: 1935 bytes --]
On Tue, 2007-10-23 at 11:10 -0400, Steven Rostedt wrote:
> --
> On Tue, 23 Oct 2007, Peter Zijlstra wrote:
> > +
> > +void plist_head_splice(struct plist_head *src, struct plist_head *dst)
> > +{
> > + struct plist_node *src_iter_first, *src_iter_last, *dst_iter;
> > + struct plist_node *tail = container_of(dst, struct plist_node, plist);
> > +
> > + dst_iter = next_prio(tail);
> > +
> > + while (!plist_head_empty(src) && dst_iter != tail) {
> > + src_iter_first = plist_first(src);
> > +
> > + src_iter_last = next_prio(src_iter_first);
> > + src_iter_last = prev_node(src_iter_last);
> > +
> > + WARN_ON(src_iter_first->prio != src_iter_last->prio);
> > + WARN_ON(list_empty(&src_iter_first->plist.prio_list));
> > +
> > + while (src_iter_first->prio > dst_iter->prio) {
> > + dst_iter = next_prio(dst_iter);
> > + if (dst_iter == tail)
> > + goto tail;
> > + }
> > +
> > + list_del_init(&src_iter_first->plist.prio_list);
> > +
> > + if (src_iter_first->prio < dst_iter->prio) {
>
> I may be confused here, but shouldn't we be linking the
> src_iter_first->prio_list somewhere here? Doesn't all different prios need
> to be in its separate prio_list? Otherwise two splices in a row can cause
> the above WARN_ON (prio != prio).
>
> > + list_add_tail(&src_iter_first->plist.node_list,
> > + &dst_iter->plist.node_list);
Uhm, yeah, that was supposed the be prio_list indeed.
Thanks!
> > + } else if (src_iter_first->prio == dst_iter->prio) {
> > + dst_iter = next_prio(dst_iter);
> > + } else BUG();
> > +
> > + list_splice2_tail(&src_iter_first->plist.node_list,
> > + &src_iter_last->plist.node_list,
> > + &dst_iter->plist.node_list);
> > + }
> > +
> > +tail:
> > + list_splice_tail_init(&src->prio_list, &dst->prio_list);
> > + list_splice_tail_init(&src->node_list, &dst->node_list);
> > +}
> >
> > --
> >
> >
> >
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-10-23 16:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 12:03 [RFC/PATCH 0/5] rt: workqueue PI support -v2 Peter Zijlstra
2007-10-23 12:03 ` [RFC/PATCH 1/5] rt: rename rt_mutex_setprio to task_setprio Peter Zijlstra
2007-10-23 12:03 ` [RFC/PATCH 2/5] rt: list_splice2 Peter Zijlstra
2007-10-23 14:08 ` Steven Rostedt
2007-10-23 12:04 ` [RFC/PATCH 3/5] rt: plist_head_splice Peter Zijlstra
2007-10-23 15:10 ` Steven Rostedt
2007-10-23 16:26 ` Peter Zijlstra [this message]
2007-10-23 17:45 ` Peter Zijlstra
2007-10-23 12:04 ` [RFC/PATCH 4/5] rt: PI-workqueue support Peter Zijlstra
2007-10-23 12:04 ` [RFC/PATCH 5/5] rt: PI-workqueue: fix barriers Peter Zijlstra
2007-10-23 19:22 ` [RFC/PATCH 6/5] rt: PI-workqueue: wait_on_work() fixup Peter Zijlstra
2007-10-23 19:22 ` [RFC/PATCH 7/5] rt: PI-workqueue: propagate prio for delayed work Peter Zijlstra
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=1193156793.6914.0.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=dwalker@mvista.com \
--cc=ghaskins@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@tv-sign.ru \
--cc=rostedt@goodmis.org \
--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