From: Jan Kiszka <jan.kiszka@domain.hid>
To: xenomai-core <xenomai@xenomai.org>
Subject: [Xenomai-core] Re: [RFC][PATCH] optimise wakeup order in xnsynch_flush
Date: Thu, 07 Sep 2006 17:44:14 +0200 [thread overview]
Message-ID: <45003E4E.9060302@domain.hid> (raw)
In-Reply-To: <45003003.7070507@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]
Jan Kiszka wrote:
> Hi,
>
> this is so far a mind experiment combined with an untested patch:
>
> [Assuming priority lists, the following is irrelevant for O(1) sched-queues]
>
> Consider we have some bulk of threads with varying priorities waiting on
> a xnsynch object. Typically, they are queued in priority order, the
> highest prio thread at the head. When we wake them up all at once via
> xnsynch_flush, we iterate from high to low prio threads.
>
> Waking up includes inserting those threads in the ready queue(s), again
> the highest prio thread first. On wake up of the first waiting thread we
> will only have to skip those threads in the ready queue that have higher
> priorities. For the second thread we already have to skip the first one
> as well on insert if it isn't of the same priority. One may continue
> this workflow...
Forget about this, there was a sign mistake: ready-queue walk already
takes place in the reverse order (from lower to higher prios), thus with
minimal iterations for the sketched scenario. Time to go home...
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
prev parent reply other threads:[~2006-09-07 15:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-07 14:43 [Xenomai-core] [RFC][PATCH] optimise wakeup order in xnsynch_flush Jan Kiszka
2006-09-07 15:44 ` Jan Kiszka [this message]
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=45003E4E.9060302@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=xenomai@xenomai.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.