Hi Everbody,
we discussed this issue here a lot. Indeed, we were putting the contents of
the VampirTrace tarball to the trunk (via the vendor branch stuff).
Then again, this is no virtue by itself, is it? So we agree to removing the
configure scripts from the SVN and having it created by the au
On Mon, 4 Feb 2008, Muhammad Atif wrote:
I am trying to port xensockets to openmpi. In principle, I have the
framework and everything, but there seems to be a small issue, I cannot
get libevent (or OPAL) to give callbacks for receive (or send) for
xensockets. I have tried to implement native c
Hi Josh, hi everybody,
we'd like to have VampirTrace enabled by default -- well, of course we do ;)
Our main reason is the potential users: As soon as they want to use our tool
they want to use it with the same configuration as the default Open MPI
installation. Making the administrator re-inst
I don't mind enabled by default - however, with a big caveat that we fix the
build system issues. With that proviso, "on" by default is fine with me.
On 2/5/08 9:00 AM, "Andreas Knüpfer" wrote:
> Hi Josh, hi everybody,
>
> we'd like to have VampirTrace enabled by default -- well, of course we
Hi all,
I am trying to implement something in the paffinity:solaris that would
allow me to specify the cpu id with striding (aka in a sequence) when
selecting which cpu ids to bind. e.g. For a cpu set that looks like
this: { 0 1 2 3 4 5 6 7 }, and stride is to 2, and offset is to 1 (which
mea
I would think that the syntax being implemented by Voltaire could be
extended to support this need, but I'll leave that up to them for comment.
On 2/5/08 5:01 PM, "Pak Lui" wrote:
> Hi all,
>
> I am trying to implement something in the paffinity:solaris that would
> allow me to specify the cp
