From: Randolph Chung <tausq@debian.org>
To: Carlos O'Donell <carlos@baldric.uwo.ca>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Spinlock patch, take 2
Date: Sun, 14 Mar 2004 23:43:46 -0800 [thread overview]
Message-ID: <20040315074346.GD2384@tausq.org> (raw)
In-Reply-To: <20040315073740.GA660@baldric.uwo.ca>
> Looks beautiful. Is it measurably faster, or just semantically more
> correct than the existing implementation? :)
i have not done any measurements. the spinlock_t stuff is needed since
we've agreed that the attribute((aligned(16)) is not sufficient to
guarantee correct alignment. the atomic-lock optimization is based on
some discussions we had a few months ago. i'd like to actually try
these, but we still don't have a bootable SMP kernel yet :(
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
next prev parent reply other threads:[~2004-03-15 7:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 6:33 [parisc-linux] Spinlock patch, take 2 Randolph Chung
2004-03-15 7:37 ` Carlos O'Donell
2004-03-15 7:43 ` Randolph Chung [this message]
2004-03-19 14:30 ` Joel Soete
2004-03-19 16:27 ` Joel Soete
2004-03-25 7:28 ` Randolph Chung
2004-03-25 6:00 ` Grant Grundler
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=20040315074346.GD2384@tausq.org \
--to=tausq@debian.org \
--cc=carlos@baldric.uwo.ca \
--cc=parisc-linux@lists.parisc-linux.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