From: Peter Zijlstra <peterz@infradead.org>
To: Pranith Kumar <bobby.prani@gmail.com>
Cc: mingo@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: regarding use of various cmpxchg* API
Date: Fri, 6 Jun 2014 16:30:38 +0200 [thread overview]
Message-ID: <20140606143038.GS13930@laptop.programming.kicks-ass.net> (raw)
In-Reply-To: <5391CD70.70703@gmail.com>
On Fri, Jun 06, 2014 at 10:17:20AM -0400, Pranith Kumar wrote:
> On 06/06/2014 03:29 AM, Peter Zijlstra wrote:
>
> >
> > Don't think that's useful. If you really want to go do something, try
> > the annotation I suggested to get the parisc/sparc32 things correct
> > again. Add the __atomic sparse address space and the store()/load()
> > accessors.
> >
>
> OK. I am not sure what you are referring to here, just started looking
> at the kernel again. Any pointers to this accessors thing?
lkml.kernel.org/r/20140603073613.GH11096@twins.programming.kicks-ass.net
prev parent reply other threads:[~2014-06-06 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 22:44 regarding use of various cmpxchg* API Pranith Kumar
2014-06-06 7:29 ` Peter Zijlstra
2014-06-06 14:17 ` Pranith Kumar
2014-06-06 14:30 ` Peter Zijlstra [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=20140606143038.GS13930@laptop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bobby.prani@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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