From: Nathan Scott <nathans@sgi.com>
To: Marc Giger <gigerstyle@gmx.ch>
Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
Dru <andru@treshna.com>,
linux-xfs@oss.sgi.com, M?ns Rullg?rd <mru@kth.se>,
linux-kernel@vger.kernel.org
Subject: Re: status of Linux on Alpha?
Date: Wed, 28 Apr 2004 16:00:03 +1000 [thread overview]
Message-ID: <20040428160003.C640934@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <20040427200830.3f485a54@vaio.gigerstyle.ch>; from gigerstyle@gmx.ch on Tue, Apr 27, 2004 at 08:08:30PM +0200
On Tue, Apr 27, 2004 at 08:08:30PM +0200, Marc Giger wrote:
> Hi Ivan,
>
> Cool!
>
> I will try your patch after I finished moving to my new flat:-)
>
> I wonder why it happens only with the XFS code. What I saw
> rw_sem is used all over the place in the kernel.
We do use the downgrade_write interface in XFS, which has
an architecture specific component and a generic component.
Its much less widely used than the rest of the rw_semaphore
code - that'd be a good spot to look if one architecture is
behaving oddly.
cheers.
--
Nathan
next prev parent reply other threads:[~2004-04-28 6:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-28 12:26 Måns Rullgård
2004-03-28 16:17 ` Ivan Kokshaysky
2004-03-28 16:19 ` Måns Rullgård
2004-03-28 16:43 ` Ivan Kokshaysky
2004-03-28 20:18 ` Marc Giger
2004-03-28 20:36 ` Måns Rullgård
2004-03-29 18:52 ` Marc Giger
2004-04-04 10:10 ` Marc Giger
2004-04-09 11:45 ` Marc Giger
2004-04-09 11:48 ` Marc Giger
2004-04-09 19:06 ` Ivan Kokshaysky
2004-04-13 17:49 ` Marc Giger
2004-04-27 16:51 ` Marc Giger
2004-04-27 17:23 ` Eric Sandeen
2004-04-27 17:57 ` Marc Giger
2004-04-27 17:55 ` Ivan Kokshaysky
2004-04-27 18:08 ` Marc Giger
2004-04-27 20:20 ` Ivan Kokshaysky
2004-04-27 20:42 ` Marc Giger
2004-04-27 21:27 ` Ivan Kokshaysky
2004-04-28 6:00 ` Nathan Scott [this message]
2004-04-28 13:13 ` Dru
2004-04-28 13:29 ` Måns Rullgård
2004-04-28 14:09 ` Ivan Kokshaysky
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=20040428160003.C640934@wobbly.melbourne.sgi.com \
--to=nathans@sgi.com \
--cc=andru@treshna.com \
--cc=gigerstyle@gmx.ch \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=mru@kth.se \
/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®