From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: [PATCH] to remove unused hcl_spinlock
Date: Mon, 10 Sep 2001 23:40:34 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805165@msgid-missing> (raw)
>>>>> On Fri, 07 Sep 2001 15:01:40 -0700, "David C. Hansen" <haveblue@us.ibm.com> said:
David.Hansen> I was looking at spinlocks in the kernel and came
David.Hansen> across hcl_spinlock. If you look at this paper:
David.Hansen> http://lse.sourceforge.net/lockhier/global-spin-lock ,
David.Hansen> you can see a part on hcl_spinlock. It is
David.Hansen> initialized. but never used. Was this lock meant to
David.Hansen> guard something? Is that thing still in the code? If
David.Hansen> it isn't, here is a patch to remove hcl_spinlock.
Just FYI: stuff in the sn/ subdirectories is SGI specific. Since I
can't test that, I try to avoid touching it and it would be up to SGI
to incorporate your patch (I suspect they have fixed that already: the
SN code hasn't been synced in a while).
--david
next reply other threads:[~2001-09-10 23:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-10 23:40 David Mosberger [this message]
2001-09-13 14:38 ` [Linux-ia64] Re: [PATCH] to remove unused hcl_spinlock John Hesterberg
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-105590698805165@msgid-missing \
--to=davidm@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