From: john cooper <john.cooper@timesys.com>
To: Sven Dietrich <sdietrich@mvista.com>
Cc: "'Steven Rostedt'" <rostedt@goodmis.org>,
"'Inaky Perez-Gonzalez'" <inaky@linux.intel.com>,
robustmutexes@lists.osdl.org, mingo@elte.hu,
linux-kernel@vger.kernel.org,
"'Esben Nielsen'" <simlo@phys.au.dk>
Subject: Re: FUSYN and RT
Date: Sat, 16 Apr 2005 09:05:48 -0400 [thread overview]
Message-ID: <42610DAC.5070506@timesys.com> (raw)
In-Reply-To: <000801c54230$73a0f940$c800a8c0@mvista.com>
Sven Dietrich wrote:
>>> /** A fuqueue, a prioritized wait queue usable from
>>
>>kernel space. */
>>
>>> struct fuqueue {
>>> spinlock_t lock;
>>> struct plist wlist;
>>> struct fuqueue_ops *ops;
>>> };
>>>
>>
>>Would the above spinlock_t be a raw_spinlock_t? This goes
>>back to my first question. I'm not sure how familiar you are
>>with Ingo's work, but he has turned all spinlocks into
>>mutexes, and when you really need an original spinlock, you
>>declare it with raw_spinlock_t.
>>
>
>
> This one probably should be a raw_spinlock.
> This lock is only held to protect access to the queues.
> Since the queues are already priority ordered, there is
> little benefit to ordering -the order of insertion-
> in case of contention on a queue, compared with the complexity.
The choice of lock type should derive from both the calling
context and the length of time the lock is expected to be held.
-john
--
john.cooper@timesys.com
next prev parent reply other threads:[~2005-04-16 13:11 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 20:35 FUSYN and RT Perez-Gonzalez, Inaky
2005-04-12 23:11 ` Esben Nielsen
2005-04-13 0:27 ` Daniel Walker
2005-04-13 15:46 ` Steven Rostedt
2005-04-13 17:33 ` Daniel Walker
2005-04-13 18:38 ` Steven Rostedt
2005-04-15 22:51 ` Bill Huey
2005-04-15 23:37 ` Inaky Perez-Gonzalez
2005-04-16 1:14 ` Steven Rostedt
2005-04-16 1:20 ` Inaky Perez-Gonzalez
2005-04-16 1:38 ` Steven Rostedt
2005-04-16 1:53 ` Inaky Perez-Gonzalez
2005-04-16 2:31 ` Steven Rostedt
2005-04-16 3:00 ` Sven Dietrich
2005-04-16 3:31 ` Steven Rostedt
2005-04-16 13:05 ` john cooper [this message]
2005-04-16 14:23 ` Steven Rostedt
2005-04-16 14:51 ` john cooper
2005-04-16 4:05 ` Inaky Perez-Gonzalez
2005-04-18 5:30 ` Bill Huey
2005-04-18 7:37 ` Sven-Thorsten Dietrich
2005-04-18 11:33 ` Steven Rostedt
-- strict thread matches above, loose matches on Subject: below --
2005-04-12 23:36 Perez-Gonzalez, Inaky
2005-04-12 23:09 Perez-Gonzalez, Inaky
2005-04-12 22:26 Perez-Gonzalez, Inaky
2005-04-12 22:33 ` Daniel Walker
2005-04-12 21:28 Perez-Gonzalez, Inaky
2005-04-12 19:35 Perez-Gonzalez, Inaky
2005-04-12 18:15 Daniel Walker
2005-04-12 20:29 ` Esben Nielsen
2005-04-12 22:15 ` Daniel Walker
2005-04-12 20:33 ` Joe Korty
2005-04-12 21:25 ` 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=42610DAC.5070506@timesys.com \
--to=john.cooper@timesys.com \
--cc=inaky@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=robustmutexes@lists.osdl.org \
--cc=rostedt@goodmis.org \
--cc=sdietrich@mvista.com \
--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 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.