From: Randolph Chung <randolph@tausq.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Grant Grundler <grundler@parisc-linux.org>,
HPPA List <parisc-linux@parisc-linux.org>
Subject: Re: [parisc-linux] ATOMIC_HASH brainfart
Date: Sun, 4 Apr 2004 17:20:26 -0700 [thread overview]
Message-ID: <20040405002026.GT750@tausq.org> (raw)
In-Reply-To: <1081123678.10091.19.camel@dhcp23.swansea.linux.org.uk>
> > Seems like someone was confused when they hacked ATOMIC_HASH macro.
> > Cacheline is 64 bytes not 256...but I've been told several times gcc
> > is smart enough to convert "foo/64" to "foo>>6"...then just use
> > the L1_CACHE_BYTES definition to indicate intent?
>
> IFF foo is a constant or foo is unsigned. Looks fine to me
or you can even use L1_CACHE_SHIFT :)
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
prev parent reply other threads:[~2004-04-05 0:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-04 6:56 [parisc-linux] ATOMIC_HASH brainfart Grant Grundler
2004-04-05 0:08 ` Alan Cox
2004-04-05 0:20 ` Randolph Chung [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=20040405002026.GT750@tausq.org \
--to=randolph@tausq.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=grundler@parisc-linux.org \
--cc=parisc-linux@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