From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: new ia64 kernel patch (relative to 2.5.69)
Date: Tue, 13 May 2003 00:29:30 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705743@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705722@msgid-missing>
>>>>> On Tue, 13 May 2003 09:38:15 +1000, Keith Owens <kaos@sgi.com> said:
Keith> Not just exponential backoff. Also kdb, checking for hung
Keith> spinlocks, calculating spinlock hold time plus any other
Keith> debugging or performance monitoring code that we can add now
Keith> that there is only one copy of the spinlock contention code.
Keith> They all need additional and separate sets of registers.
Why do they need separate sets of registers?
Please show some real code that justifies the number of registers you
want to add. The cost may be small, but it's certainly not zero.
--david
prev parent reply other threads:[~2003-05-13 0:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 14:02 [Linux-ia64] Re: new ia64 kernel patch (relative to 2.5.69) Keith Owens
2003-05-12 23:20 ` David Mosberger
2003-05-12 23:38 ` Keith Owens
2003-05-13 0:01 ` Keith Owens
2003-05-13 0:25 ` David Mosberger
2003-05-13 0:29 ` David Mosberger [this message]
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-105590723705743@msgid-missing \
--to=davidm@napali.hpl.hp.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