All of lore.kernel.org
 help / color / mirror / Atom feed
From: dave.martin@linaro.org (Dave Martin)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM cortex A9 performance issue
Date: Thu, 7 Jul 2011 16:27:40 +0100	[thread overview]
Message-ID: <20110707152740.GG2486@arm.com> (raw)
In-Reply-To: <CAE_nTV4VgcNB0gc64zEPEfHp-hnDBsw6QsM=GqEObXAwzMTzTA@mail.gmail.com>

On Thu, Jul 07, 2011 at 02:48:05PM +0530, rd bairva wrote:
> Hi,
> 
> We are trying to benchmark ARM cortex A9 dual core behavior with
> respect to single core
> performance and also measuring it with respect to x86 dual core/single core.
> Please find attached with the mail is c app which we are using for benchmarking.
> 
> Simple overview of C application:
> - It creates a shared memory area using shm_open().
>   in this shm area, it declares 2 Process shared pthread mutex, lets say L1, L2.
> - then it forks to create a server_task and client task.
> - server_task takes L1 lock, touches a shm area, unlock L2, in a loop.
> - client_task takes L2 lock, touches a shm area, unlock L1, in a loop.
> - This loop runs for N number of times that we measure.

The behaviour of pthread_mutex_unlock is unspecified if an attempt is made
to ulock a mutex from a thread which doesn't currently own that mutex.
You probably need to re-code your test to avoid this incorrect use of
the ABI before an interpretation can be placed on the results.

See pthread_mutexattr_init(3) for details.



Some people have been reported issues related to  process shared mutexes
on ARM recently:

https://bugs.launchpad.net/ubuntu/+source/apr/+bug/604753

I'm not sure of the current status of that though, and I don't know
whether it would affect your test or not.

Cheers
---Dave

> 
> Here are the results for N/sec for different CPUs.
> 
> Platform              Up cores              req/sec                cpuload
> Cortexa9                    2                              ~44000
>             100%
> Cortexa9                    1                              ~18000
>             100%
> X86                            2                              ~64000
>                35%
> X86                            1                              ~458886
>              100%     (1 cpu down by sysfs)
> 
> we are not able to understand the results.
> - why for coretx A9 both dual/single core we are getting 100% cpu usage.
> - why in case of x86, N/sec is very high for single core than dual core.
> - why single core N/s is 1/3 in case of CortexA9.
> 
> Thanks,
> Ramdayal


> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2011-07-07 15:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-07  9:18 ARM cortex A9 performance issue rd bairva
2011-07-07 15:27 ` Dave Martin [this message]
2011-07-08 11:38   ` rd bairva
2011-07-08 13:33     ` Dave Martin
2011-07-11  8:26       ` rd bairva
2011-07-11 17:00         ` Dave Martin

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=20110707152740.GG2486@arm.com \
    --to=dave.martin@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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.