I'm afraid it is still under development, though hopefully we'll have
some prelim stuff available in another month or so. We'll send a note
to the devel list when we have something (though it will likely be
rough for now).
On Aug 18, 2008, at 9:37 AM, Bogdan Costescu wrote:
On Mon, 18 A
On Mon, 18 Aug 2008, Ralph Castain wrote:
For other purposes, some of us have been looking at a "profiling"
tool that would be run on a cluster and output a "recommended" mca
param file to optimize OMPI's behavior for that environment.
Is there such a tool already available ? I'd be very much
We don't really need a finer grain knowledge about the processor at
compile time.
There are some other open-source projects which have already done
something very similar if not identical; one of them is the media
player mplayer (http://www.mplayerhq.hu/). Why not using these as
starting po
For other purposes, some of us have been looking at a "profiling" tool
that would be run on a cluster and output a "recommended" mca param
file to optimize OMPI's behavior for that environment. The idea was
that a sys admin would launch this once across the cluster so we could
do things lik
We don't really need a finer grain knowledge about the processor at
compile time. The only thing we should detect is if a bit of code can
or cannot be compiled. We can deal with the processor characteristics
at runtime. I imagine that most of today processors have the
capability of exportin
I obviously won't be in Dublin (I'll be in a fishing boat in the
middle of nowhere Canada -- much better), so I'm going to chime in now.
The m4 part actually isn't too bad and is pretty simple. I'm not sure
other than looking at some variables set by ompi_config_asm that there
is much to c
Let's talk about this in Dublin. I can probably help with the m4
magic, but I need to understand exactly what needs to be done first.
On Aug 16, 2008, at 11:51 AM, Terry Dontje wrote:
George Bosilca wrote:
The intent of the memcpy framework is to allow a selection between
several memcpy a
George Bosilca wrote:
The intent of the memcpy framework is to allow a selection between
several memcpy at runtime. Of course, there will be a preselection at
compile time, but all versions that can compile on a given
architecture will be benchmarked at runtime and the best one will be
selecte
The intent of the memcpy framework is to allow a selection between
several memcpy at runtime. Of course, there will be a preselection at
compile time, but all versions that can compile on a given
architecture will be benchmarked at runtime and the best one will be
selected. There is a file
Hi Tim,
Thanks for bringing the below up and asking for a redirection to the
devel list. I think looking/using the MCA memcpy framework would be a
good thing to do and maybe we can work on this together once I get out
from under some commitments. However, some of the challenges that
original
10 matches
Mail list logo
