From: Christoph Hellwig <hch@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Bill Huey <bhuey@lnxw.com>, Esben Nielsen <simlo@phys.au.dk>,
Christoph Hellwig <hch@infradead.org>,
Daniel Walker <dwalker@mvista.com>, Dave Chinner <dgc@sgi.com>,
greg@kroah.com, Nathan Scott <nathans@sgi.com>,
Steve Lord <lord@xfs.org>,
linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com
Subject: Re: RT and XFS
Date: Tue, 19 Jul 2005 14:27:50 +0100 [thread overview]
Message-ID: <20050719132750.GA20595@infradead.org> (raw)
In-Reply-To: <20050719123457.GC12368@elte.hu>
On Tue, Jul 19, 2005 at 02:34:57PM +0200, Ingo Molnar wrote:
> (I do disagree with Christoph on another point: i do think we eventually
> want to change the standard semaphore type in a similar fashion upstream
> as well - but that probably has to come with a s/struct semaphore/struct
> mutex/ change as well.)
Actually having a mutex_t in mainline would be a good idea even without
preempt rt, to document better what kind of locking we expect.
next prev parent reply other threads:[~2005-07-19 13:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 23:01 RT and XFS Daniel Walker
2005-07-12 23:39 ` William Weston
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 [this message]
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=20050719132750.GA20595@infradead.org \
--to=hch@infradead.org \
--cc=bhuey@lnxw.com \
--cc=dgc@sgi.com \
--cc=dwalker@mvista.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=lord@xfs.org \
--cc=mingo@elte.hu \
--cc=nathans@sgi.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.