mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Pranith Kumar <bobby.prani@gmail.com>
Cc: catalin.marinas@arm.com, LKML <linux-kernel@vger.kernel.org>, tony@bake
Subject: Re: [PATCH 1/1] prefetch result for ARM64 atomic ops
Date: Mon, 14 Apr 2014 11:29:13 -0700	[thread overview]
Message-ID: <1397500153.2962.11.camel@joe-AO722> (raw)
In-Reply-To: <CAJhHMCCPd3+AddjK2S==4jii5G5q7ioNOjJ-0ds0u6YYVeBaoQ@mail.gmail.com>

On Mon, 2014-04-14 at 14:11 -0400, Pranith Kumar wrote:
> On Mon, Apr 14, 2014 at 2:04 PM, Joe Perches <joe@perches.com> wrote:
> > Are there some benchmark comparison results
> > you neglected to attach?
> 
> I was trying to get these ops to be similar to the 32 bit atomic ops which
> all have prefetch. I did not see any reason why we shouldn't do the same
> here. But no, no hard numbers yet.

Then you should probably send this as an RFC patch.

> >> diff --git a/arch/arm64/include/asm/atomic.h b/arch/arm64/include/asm/atomic.h
> >> +    prefetchw(&v->counter);
> >
> > Does this compile?

> Argh, my mistake! I overlooked this. Please find fixed patch below:
[]
> diff --git a/arch/arm64/include/asm/atomic.h b/arch/arm64/include/asm/atomic.h
[]
> @@ -235,6 +244,7 @@ static inline long atomic64_cmpxchg(atomic64_t
> *ptr, long old, long new)
>      unsigned long res;
> 
>      smp_mb();
> +    prefetchw(&v->counter);

It seems you sent the original patch again, still not compiled.

An arm64 cross-compiler is available here:
http://linuxdriverproject.org/mediawiki/index.php/Cross-compiling_Linux_kernel_on_x86_64#Installing_arm64_cross-compiler

It'd be nice if an arm64 toolchain was on the kernel.org list too
https://www.kernel.org/pub/tools/crosstool/




  reply	other threads:[~2014-04-14 18:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-14 17:55 Pranith Kumar
2014-04-14 18:04 ` Joe Perches
2014-04-14 18:11   ` Pranith Kumar
2014-04-14 18:29     ` Joe Perches [this message]
2014-04-14 18:32       ` Pranith Kumar

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=1397500153.2962.11.camel@joe-AO722 \
    --to=joe@perches.com \
    --cc=bobby.prani@gmail.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony@bake \
    /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

all inboxes | Powered by JetHome®