Hi Malek,

Thanks a lot for the clarifications.

Regards,
Shervin

--- On Tue, 7/24/12, [email protected] <[email protected]> 
wrote:

Message: 4
Date: Tue, 24 Jul 2012 14:56:48 -0400
From: Malek Musleh <[email protected]>
To: gem5 users mailing list <[email protected]>
Subject: Re: [gem5-users] assign one thread per core in Parsec
    (biswabandan    panda)
Message-ID:
    <capoxfjxzfen7x8cxmqomm5b_6vjanrpvwc4c38xdnxuk0na...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

The GOMP_CPU_AFFINITY will only work for OpenMP benchmarks (of which only a
subset of the parsec benchmarks have OMP versions). For pthread
implementations (including Splash2 benchmarks) you have to use
pthread_affinity() scheduling, requiring you to modify the benchmark source
code.

There are comments in the splash2 code that indicate where it would be
advisable to pin the threads to cores.

The GOM_CPU_AFFINITY is an environment variable, from which the OMP clauses
will check at run-time for. You can even set that variable from within the
benchmark source code as well (I am sure google can provide a better and
more detailed explanation)

Malek

On Tue, Jul 24, 2012 at 2:25 PM, shervin hajiamini
<[email protected]>wrote:

> Hi Biswabandan,
>
> Thank you very much for your help. If I want to have 32 cores, shall I add
> the following to .rcS script file?
>
> GOMP_CPU_AFFINITY = "0 1 2 3 ...31".
>
> Or is there another way for system with greater number of cores?
>
> Can I apply this method for SPLASH-2 benchmark as well?
>
> Thanks,
> Shervin
>
> --- On *Tue, 7/24/12, [email protected] <
> [email protected]>* wrote:
>
> Message: 4
> Date: Tue, 24 Jul 2012 07:56:06 +0530
> From: biswabandan panda 
> <[email protected]<http://mc/[email protected]>
> >
> To: gem5 users mailing list 
> <[email protected]<http://mc/[email protected]>
> >
> Subject: Re: [gem5-users] assign one thread per core in Parsec
> Message-ID:
>     
><CADFuLAtoyXYq00D7ZiJrar1sm=V=PN5Jo4pycP=jukjlfee...@mail.gmail.com<http://mc/[email protected]>
> >
> Content-Type: text/plain; charset="windows-1252"
>
> export GOMP_CPU_AFFINITY="0 1 2 3"
>
> put this if u r using 4 core system with 4 threads. it ll pin the threads
>
> On Tue, Jul 24, 2012 at 7:35 AM, shervin hajiamini
> <[email protected] <http://mc/[email protected]>
> >wrote:
>
> > Hi all,
> >
> >
> >
> > I am running PARSEC suit (canneal) on 4 cores (O3). The workload is NOT
> > equally distributed among the cores. As I have created canneal?s .rcS
> file
> > with 4 threads, could anybody please let me know how I can assign JUST
> one
> > thread per core in PARSEC so that the total workload is distributed
> equally
> > among the cores?
> >
> >
> >
> > Regards,
> >
> > Shervin
> >
> > _______________________________________________
> > gem5-users mailing list
> > [email protected] <http://mc/[email protected]>
> > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
> >
>
>
>
> --
>
> *thanks&regards
> *
> *BISWABANDAN*
> *Any intelligent fool can make things bigger, more complex, and more
> violent.
> It takes a touch of genius - and a lot of courage - to move in the opposite
> direction.*
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://m5sim.org/cgi-bin/mailman/private/gem5-users/attachments/20120724/d94ef3e0/attachment-0001.html
> >
>
> ------------------------------
>
>
> _______________________________________________
> gem5-users mailing list
> [email protected]
> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://m5sim.org/cgi-bin/mailman/private/gem5-users/attachments/20120724/808a002a/attachment.html>

------------------------------

_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

End of gem5-users Digest, Vol 72, Issue 59
******************************************
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Reply via email to