mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: William Weston <weston@sysex.net>
To: Daniel Walker <dwalker@mvista.com>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: RT and XFS
Date: Tue, 12 Jul 2005 16:39:58 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0507121630150.21776@echo.lysdexia.org> (raw)
In-Reply-To: <1121209293.26644.8.camel@dhcp153.mvista.com>

On Tue, 12 Jul 2005, Daniel Walker wrote:

> Is there something so odd about the XFS locking, that it can't use the
> rt_lock ?
> 
> 
> --- linux.orig/fs/xfs/linux-2.6/mrlock.h
> +++ linux/fs/xfs/linux-2.6/mrlock.h
> @@ -37,12 +37,12 @@
>  enum { MR_NONE, MR_ACCESS, MR_UPDATE };
>  
>  typedef struct {
> -	struct rw_semaphore	mr_lock;
> -	int			mr_writer;
> +	struct compat_rw_semaphore	mr_lock;
> +	int				mr_writer;
>  } mrlock_t;

BTW, what's the difference between rw_semaphore and compat_rw_semaphore?  
Or between semaphore and compat_semaphore?  I ran into a similar issue
(needing compat_semaphore) with the IVTV drivers.  The following is a
portion of my patch to get IVTV running under RT (the other portions are
just compile-time semantics):

--- ivtv-0.2.0-rc3k.orig/driver/msp3400.c       2004-11-19 08:21:04.000000000 -0800
+++ ivtv-0.2.0-rc3k/driver/msp3400.c    2005-06-22 17:26:24.000000000 
-0700
@@ -115,7 +115,7 @@
 	struct task_struct  *thread;
 	wait_queue_head_t    wq;
 
-	struct semaphore    *notify;
+	struct compat_semaphore *notify;
 	int                  active,restart,rmmod;
 
 	int                  watch_stereo;

--ww

  reply	other threads:[~2005-07-12 23:43 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-12 23:01 Daniel Walker
2005-07-12 23:39 ` William Weston [this message]
2005-07-13  0:25 ` Nathan Scott
2005-07-13  0:41   ` Daniel Walker
2005-07-13  0:37     ` Nathan Scott
2005-07-13  6:47   ` Ingo Molnar
2005-07-13 16:45     ` Daniel Walker
2005-07-14  0:22       ` Nathan Scott
2005-07-14  3:50         ` Dave Chinner
2005-07-14  4:10           ` Daniel Walker
     [not found]             ` <20050714052347.GA18813@elte.hu>
2005-07-14 15:56               ` Daniel Walker
2005-07-14 16:08                 ` Christoph Hellwig
2005-07-18 12:10                   ` Esben Nielsen
2005-07-19  3:26                     ` Bill Huey
2005-07-19 12:34                       ` Ingo Molnar
2005-07-19 13:27                         ` Christoph Hellwig
2005-07-19 13:50                           ` Ingo Molnar
2005-07-14 16:08                 ` Christoph Hellwig
2005-07-15 10:23             ` Ingo Molnar
2005-07-15 16:16               ` Daniel Walker
2005-07-18 11:33                 ` Esben Nielsen
2005-07-19  3:31                 ` Bill Huey

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=Pine.LNX.4.58.0507121630150.21776@echo.lysdexia.org \
    --to=weston@sysex.net \
    --cc=dwalker@mvista.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

all inboxes | Powered by JetHome®