From: Chuck Ebbert <76306.1226@compuserve.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org, ak@suse.de,
mingo@elte.hu, Andrew Morton <akpm@osdl.org>
Subject: Re: [patch 2.6.13-rc6] i386: semaphore ownership tracking
Date: Sun, 21 Aug 2005 05:47:36 -0400 [thread overview]
Message-ID: <200508210550_MC3-1-A7CF-D29F@compuserve.com> (raw)
On Sat, 20 Aug 2005 15:01:27 -0400, Lee Revell wrote:
> How is it different from the ownership tracking used for PI in the -rt
> kernel?
Those are a completely new type of mutex (rt_mutex.) Mine is a very
low-overhead (3 extra instructions in down()) addition to the normal
Linux semaphores. I guess they are called compat_semaphores in -rt,
and I didn't see any ownership tracking for them in the -rt patch.
__
Chuck
next reply other threads:[~2005-08-21 9:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-21 9:47 Chuck Ebbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-20 7:07 [patch 2.6.13-rc6] i386: semaphore ownership tracking Chuck Ebbert
2005-08-20 19:01 ` Lee Revell
2005-08-20 2:54 Chuck Ebbert
2005-08-20 3:02 ` Andrew Morton
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=200508210550_MC3-1-A7CF-D29F@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rlrevell@joe-job.com \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox