Date: | Fri, 26 May 2006 16:14:10 -0600 |
---|---|
From: | "Abhishek Ranjan" <absk82@xxxxxxxxx> |
Subject: | Re: [Gems-users] Functional Unit latencies on Ruby |
thanks a lot Mike!
This means that ruby will give us the memory accesses and the number of cycles assuming that computational units all have single cycles latency and no resource constraint.
If we have a code like this:
for( some condition)
{
memory access
FP Add
FP Add
FP Mul
}
then the number of cycles elapsed between two consecutive memory accesses will be three as given by ruby though it will depends a lot on the functional unit latencies. Is that correct? If yes, I think I would be better off using Opal with ruby.
the number of cycles which we get as the output of dump stats are simics cycles right? which will be twice that of ruby cycles if SIMICS_RUBY_MULTIPLIER if set to 2.
Thanks a lot,
Abhishek
On 5/26/06, Mike Marty <mikem@xxxxxxxxxxx> wrote:
Mike Marty wrote: |
[← Prev in Thread] | Current Thread | [Next in Thread→] |
---|---|---|
|
Previous by Date: | Re: [Gems-users] Failed assertion in DirectoryMemory.C, Mike Marty |
---|---|
Next by Date: | Re: [Gems-users] addLogEntry and addMagicEntry, James Wang |
Previous by Thread: | Re: [Gems-users] Functional Unit latencies on Ruby, Mike Marty |
Next by Thread: | Re: [Gems-users] Functional Unit latencies on Ruby, Mike Marty |
Indexes: | [Date] [Thread] |