6/2012 04:54 PM, Holger Mickler wrote:
> Hi Gene,
>
> this error is often caused by insufficiently synchronized TSCs (time stamp
> counter) of different processors/cores.
> When VT uses the TSC for timing the events (it does that by default), and the
> processes switch to anot
Hi Gene,
this error is often caused by insufficiently synchronized TSCs (time stamp
counter) of different processors/cores.
When VT uses the TSC for timing the events (it does that by default), and the
processes switch to another core during execution, it may well happen that the
next recorded tim
uring the following time period.
>>> - 5:00am-11:00am Pacific US time
>>> - 6:00am-12:00pm Mountain US time
>>> - 7:00am-1:00pm Central US time
>>> - 8:00am-2:00pm Eastern US time
>>> - 12:00pm-6:00pm GMT
>>>
>>> Please let me know if
Jeff Squyres wrote:
> On May 27, 2009, at 6:49 AM, Holger Mickler wrote:
>
>> would you mind sharing this patch? We'd like to test our current VT
>> version with
>> some MPI RMA code :)
>>
>
> No problem-o. I've submitted this patch upstream to
Hi Jeff, all,
would you mind sharing this patch? We'd like to test our current VT version with
some MPI RMA code :)
Does anyone know of some (small) code/benchmark that uses all available MPI RMA
functionality? As far as I see, IMB only uses fence and put/get/accumulate. No
locks or post/wait/sta
uot;, there is the phrase
"VampirTrace has been developed at ZI, TU Dresden"
which must read
"...developed at ZIH, TU Dresden" (the 'H' is missing from ZIH)
Thanks,
Holger
--
Holger Mickler
Technische Universität Dresden
Center for Information Services
and H
