public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] ia64_spinlock_contention and NEW_LOCK
Date: Wed, 12 Mar 2003 01:38:32 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709806043@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709806001@msgid-missing>

On Tue, 11 Mar 2003 14:37:23 -0800, 
David Mosberger <davidm@napali.hpl.hp.com> wrote:
>>>>>> On Sat, 08 Mar 2003 00:57:04 +1100, Keith Owens <kaos@sgi.com> said:
>
>  Keith> 2.4.0-test6-ia64-000811 introduced ia64_spinlock_contention
>  Keith> and NEW_LOCK.  AFAICT they have been disabled ever since they
>  Keith> were introduced.  Are there any plans to use this NEW_LOCK
>  Keith> code?
>
>I still think it would make sense to have back-off logic in the
>spinlock contention case, but given that I haven't had time to work on
>it in the last 2 years and nobody else has expressed interest in it, I
>think it's time to just nuke the code.  If someone wants to work on it
>later on, it's been archived often enough that the code can be dug out
>if necessary.

Can you remember what was wrong with the out of line contention code?
The obvious problems are the lack of unwind data, it will not work for
spin locks in modules (PCREL21B will not reach from region 5 to region
7) and the fact that ar.pfs gets corrupted (gcc 2.96 does not recognise
that ar.pfs in the clobber list means leaf functions must now save
ar.pfs).  Were there any other problems?



  parent reply	other threads:[~2003-03-12  1:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-07 13:57 [Linux-ia64] ia64_spinlock_contention and NEW_LOCK Keith Owens
2003-03-11 22:37 ` David Mosberger
2003-03-12  1:38 ` Keith Owens [this message]
2003-03-12  1:59 ` David Mosberger

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=marc-linux-ia64-105590709806043@msgid-missing \
    --to=kaos@sgi.com \
    --cc=linux-ia64@vger.kernel.org \
    /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