public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Korty <joe.korty@ccur.com>
To: Daniel Walker <dwalker@mvista.com>
Cc: linux-kernel@vger.kernel.org, inaky.perez-gonzalez@intel.com,
	mingo@elte.hu
Subject: Re: FUSYN and RT
Date: Tue, 12 Apr 2005 16:33:29 -0400	[thread overview]
Message-ID: <20050412203329.GA15304@tsunami.ccur.com> (raw)
In-Reply-To: <1113329702.23407.148.camel@dhcp153.mvista.com>

On Tue, Apr 12, 2005 at 11:15:02AM -0700, Daniel Walker wrote:

> It seems like these two locks are going to interact on a very limited
> basis. Fusyn will be the user space mutex, and the RT mutex is only in
> the kernel. You can't lock an RT mutex and hold it, then lock a Fusyn
> mutex (anyone disagree?). That is assuming Fusyn stays in user space.

Well yeah, but you could lock a fusyn, then invoke a system call which
locks a kernel semaphore.

Regards,
Joe
--
"Money can buy bandwidth, but latency is forever" -- John Mashey

  parent reply	other threads:[~2005-04-12 23:21 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-12 18:15 FUSYN and RT Daniel Walker
2005-04-12 20:29 ` Esben Nielsen
2005-04-12 22:15   ` Daniel Walker
2005-04-12 20:33 ` Joe Korty [this message]
2005-04-12 21:25   ` Daniel Walker
  -- strict thread matches above, loose matches on Subject: below --
2005-04-12 19:35 Perez-Gonzalez, Inaky
2005-04-12 20:35 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
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
2005-04-12 21:28 Perez-Gonzalez, Inaky
2005-04-12 22:26 Perez-Gonzalez, Inaky
2005-04-12 22:33 ` Daniel Walker
2005-04-12 23:09 Perez-Gonzalez, Inaky
2005-04-12 23:36 Perez-Gonzalez, Inaky

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=20050412203329.GA15304@tsunami.ccur.com \
    --to=joe.korty@ccur.com \
    --cc=dwalker@mvista.com \
    --cc=inaky.perez-gonzalez@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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