From: Jan Kiszka <jan.kiszka@domain.hid>
To: rpm@xenomai.org
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [Fwd: [rfc][patch] queued spinlocks (i386)]
Date: Fri, 23 Mar 2007 15:45:17 +0100 [thread overview]
Message-ID: <4603E7FD.4010207@domain.hid> (raw)
In-Reply-To: <1174660491.4606.17.camel@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1183 bytes --]
Philippe Gerum wrote:
> On Fri, 2007-03-23 at 14:47 +0100, Jan Kiszka wrote:
>> That idea sounds worthwhile for xnlocks as well, doesn't it?
>
> Not sure, yet. Real starvation on xnlocks would require non-RT activity
> to be completely locked out on all CPUs in the first place for that to
> happen, which would be the sign of a serious design flaw. I see no way
> to solve such initial problem by adding some fairness to the lock
> dispatching policy in primary mode.
I wasn't primarily thinking about avoiding starvation (would indeed be
bad if a system suffers from such a risk) but about making spinlock
contention more predictable in case that successive (but bounded) lock
acquisitions may occur.
>
> Still, thinking about this patch, since there is a price to pay for this
> approach due to serious cache-bouncing on high contention, using the
> waiter priority to manage the pending queue instead of a simple FIFO
> ticketing would be at least logically better, but likely even more
> costly.
Yeah, I thought about such approaches as well before. Don't have my
drafts on this at hand, but it was costly, specifically /wrt spinlock size.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2007-03-23 14:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-23 13:47 [Xenomai-core] [Fwd: [rfc][patch] queued spinlocks (i386)] Jan Kiszka
2007-03-23 14:34 ` Philippe Gerum
2007-03-23 14:45 ` Jan Kiszka [this message]
2007-03-23 15:05 ` Philippe Gerum
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=4603E7FD.4010207@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=rpm@xenomai.org \
--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.