From: Andi Kleen <ak@suse.de>
To: Jimi Xenidis <jimix@watson.ibm.com>
Cc: rusty@rustcorp.com.au, xen-devel@lists.xensource.com
Subject: Re: My turn to rant about types... bitops
Date: Thu, 6 Oct 2005 17:19:26 +0200 [thread overview]
Message-ID: <200510061719.26806.ak@suse.de> (raw)
In-Reply-To: <F93C26C9-3738-4320-BDAF-C250B505B069@watson.ibm.com>
On Thursday 06 October 2005 17:10, Jimi Xenidis wrote:
> On Oct 6, 2005, at 9:39 AM, Andi Kleen wrote:
> > Jimi Xenidis <jimix@watson.ibm.com> writes:
> >> adding 32bit bitops but I doubt I'd be able to do that in
> >> Linux which does not provide "u32" bitops.
> >
> > Actually it does - when the arch has ARCH_HAS_ATOMIC_UNSIGNED set
> > it's allowed with the normal bitops.
>
> Its not set for linuxppc64, bitops use longs so the code is optimized
> for them.
Well, that's a specific linuxppc64 limitation.
-Andi
next prev parent reply other threads:[~2005-10-06 15:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 16:52 My turn to rant about types... bitops Jimi Xenidis
2005-10-05 18:17 ` Keir Fraser
2005-10-06 11:32 ` Jimi Xenidis
2005-10-06 13:39 ` Andi Kleen
2005-10-06 15:10 ` Jimi Xenidis
2005-10-06 15:19 ` Andi Kleen [this message]
[not found] ` <7D88E873-B404-4E28-BE87-D474F67CAA82@watson.ibm.com>
2005-10-06 12:49 ` Keir Fraser
2005-10-10 11:44 ` Rusty Russell
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=200510061719.26806.ak@suse.de \
--to=ak@suse.de \
--cc=jimix@watson.ibm.com \
--cc=rusty@rustcorp.com.au \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.