Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Richard Hirst <rhirst@linuxcare.com>
To: parisc-linux@thepuffingroup.com
Subject: Re: tar hangs on 715/75 (spinlock problem)
Date: Mon, 22 Jan 2001 22:17:04 +0000	[thread overview]
Message-ID: <20010122221704.R3571@linuxcare.com> (raw)
In-Reply-To: <20010122213219.Q3571@linuxcare.com>; from rhirst@linuxcare.com on Mon, Jan 22, 2001 at 09:32:19PM +0000

On Mon, Jan 22, 2001 at 09:32:19PM +0000, Richard Hirst wrote:
> On Mon, Jan 22, 2001 at 04:50:14PM +0000, Richard Hirst wrote:
> > Hi,
> >   tar (and nscd) hang on my 715/75.  Same binaries/libraries work on
> > the B180.  The hang is in __pthread_acquire() called from
> 
> This is because ldcw behaves differently on the 715/75 and the B180.

Grant tells me spinlock words have to be the first word of a cacheline,
so that would be why my example code broke.  However, libpthreads uses
spinlocks and doesn't appear to force any alignment.

I think the libpthreads spinlock definitions come from
glibc/linuxthreads/sysdeps/pthread/bits/pthreadtypes.h, struct
pthread_mutex_t, spinlock is inside __m_lock.  No alignment is
specified.  When debugging tar, I found the spinlock word at
0x4014df4c.

Richard

  reply	other threads:[~2001-01-22 22:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-22 16:50 [parisc-linux] tar hangs on 715/75 Richard Hirst
2001-01-22 17:44 ` Greg Ingram
2001-01-22 21:32 ` tar hangs on 715/75 (spinlock problem) Richard Hirst
2001-01-22 22:17   ` Richard Hirst [this message]
2001-01-23  0:17     ` Grant Grundler
2001-01-23  0:38       ` Ulrich Drepper
  -- strict thread matches above, loose matches on Subject: below --
2001-01-23  0:41 John Marvin

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=20010122221704.R3571@linuxcare.com \
    --to=rhirst@linuxcare.com \
    --cc=parisc-linux@thepuffingroup.com \
    /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