From: Joel Soete <soete.joel@scarlet.be>
To: Kyle McMartin <kyle@mcmartin.ca>
Cc: parisc-linux <parisc-linux@lists.parisc-linux.org>,
Matthew Wilcox <matthew@wil.cx>
Subject: Re: [parisc-linux] Just A suggestion to highlight mb() and cpu_relax() in s files?
Date: Thu, 24 Aug 2006 18:39:23 +0000 [thread overview]
Message-ID: <44EDF25B.6070309@scarlet.be> (raw)
In-Reply-To: <20060824161532.GA1455@athena.road.mcmartin.ca>
Kyle McMartin wrote:
> On Thu, Aug 24, 2006 at 09:47:21AM -0600, Matthew Wilcox wrote:
>
>>I like the idea. How about using the function name instead, though?
>>
>>+#define __mb(s) __asm__ __volatile__(s "()":::"memory") /* barrier() */
>>+#define mb() __mb("mb")
>>+#define rmb() __mb("rmb")
>>+#define wmb() __mb("wmb")
>>+#define smp_mb() __mb("smp_mb")
>
>
Love it too (would be my next q)
anyway won't we need some comment charater: I prefer ';' (my oldfashion) but may be better '#'
+#define __mb(s) __asm__ __volatile__("# " s "()":::"memory") /* barrier() */
> I liek it.
Will you do it or do you prefer I send you (tomorrow) a patch?
TIA,
Joel
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
>
>
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next parent reply other threads:[~2006-08-24 18:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <J4IE0Y$F96BD8695898C37EEF35C0BA6880F173@scarlet.be>
[not found] ` <20060824154721.GL24068@parisc-linux.org>
[not found] ` <20060824161532.GA1455@athena.road.mcmartin.ca>
2006-08-24 18:39 ` Joel Soete [this message]
2006-08-25 12:39 [parisc-linux] Just A suggestion to highlight mb() and cpu_relax() in s files? Joel Soete
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=44EDF25B.6070309@scarlet.be \
--to=soete.joel@scarlet.be \
--cc=kyle@mcmartin.ca \
--cc=matthew@wil.cx \
--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 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.