mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marc Giger <gigerstyle@gmx.ch>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: 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: Tue, 27 Apr 2004 20:08:30 +0200	[thread overview]
Message-ID: <20040427200830.3f485a54@vaio.gigerstyle.ch> (raw)
In-Reply-To: <20040427215514.A651@den.park.msu.ru>

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.

Thank you and Dru for the work and hopefully it will fix my problem.

Regards

Marc


On Tue, 27 Apr 2004 21:55:14 +0400
Ivan Kokshaysky <ink@jurassic.park.msu.ru> wrote:

> On Tue, Apr 27, 2004 at 06:51:24PM +0200, Marc Giger wrote:
> > What's the current status of the problem?
> 
> Hopefully resolved - thanks to Dru <andru@treshna.com>, who provided
> an easy way to reproduce the problem.
> 
> What we have in lib/rwsem.c:__rwsem_do_wake():
> 	int woken, loop;
> 	^^^
> and several lines below:
> 	loop = woken;
> 	woken *= RWSEM_ACTIVE_BIAS-RWSEM_WAITING_BIAS;
> 	woken -= RWSEM_ACTIVE_BIAS;
> 
> However, rw_semaphore->count is 64-bit on Alpha, so
> RWSEM_WAITING_BIAS has been defined as -0x0000000100000000L.
> Obviously, this blows up in the write contention case.
> 
> Ivan.
> 
> --- linux.orig/lib/rwsem.c	Mon Apr 26 20:11:36 2004
> +++ linux/lib/rwsem.c	Tue Apr 27 20:04:14 2004
> @@ -40,8 +40,7 @@ static inline struct rw_semaphore *__rws
>  {
>  	struct rwsem_waiter *waiter;
>  	struct list_head *next;
> -	signed long oldcount;
> -	int woken, loop;
> +	signed long oldcount, woken, loop;
>  
>  	rwsemtrace(sem,"Entering __rwsem_do_wake");
>  
> 
> 

  reply	other threads:[~2004-04-27 18:09 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 [this message]
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
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=20040427200830.3f485a54@vaio.gigerstyle.ch \
    --to=gigerstyle@gmx.ch \
    --cc=andru@treshna.com \
    --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®