- Change all uses of *printf'ing a size_t to use an explicit cast to
(unsigned long) and the %lu escape
- change ORTE_GPR_REPLICA_MAX_SIZE to INT_MAX until bug 1345 is fixed
(i.e., until we allow size_t in MCA params)
- ns_base_local_fns.c:orte_ns_base_get_proc_name_string(): changed
from %0X -> %lu
- ORTE_NAME_ARGS added explicit (unsigned long) casts, and changed all
usages of ORTE_NAME_ARGS to use %lu's
This commit was SVN r5644.
As an FYI: the pack/unpack routines should be happy with a NULL string (and appear to be so). Issue here was that the constructor was not called, which means that the string pointer was not initialized to NULL as it ordinarily would have been.
This commit was SVN r5639.
1. Instead of removing various src/ component directories, simply
"flatten" the Makefile.am structure by having only a single
top-level Makefile.am for the component, and having it include
src/Makefile.extra (which is where the source files are listed).
This effectively makes the build faster because "make" does not
traverse down into src/, and we don't build a Makefile for that
directory.
2. Did end up moving topo/unity/src/* into topo/unity, which is where
I figured out that option #1 would be a bit easier (and safer,
considering that other developers are actively working in various
src/ directories -- moving things around while they're working
would be Bad!)
3. Did not consolidate most of the io/romio component because of the
nightmare of sym links (especially w.r.t. VPATH builds) in the
included ROMIO distribution. I wasted too much time trying to get
that stuff right and finally gave up -- this is a "low hanging
fruit" optimization, after all.
This commit was SVN r5629.
- sends/recvs short messages (less than first frag size)
- does not properly ACK messages, so Ssend() is borked
- leaks memory like there's no tomorrow
- don't use it just yet
This commit was SVN r5625.
1. Added pid_t to the dps
2. Processes now "register" their local pid and update their location (i.e., nodename) on the registry during mpi_init
3. Added a new error code for values that exceed maximum for their data type (useful when transitioning a value from one variable to another of different size)
4. Fixed a few places where size_t was being incorrectly handled
5. Updated dps_test to cover pid_t types
This should now provide support for TotalView connection - which David is pursuing.
This commit was SVN r5623.
biggie), so we gain nothing there. On 10.4, it's implemented directly,
but doesn't support devices (which messes up pty support and IO
forwarding).
This commit was SVN r5621.
on all 64 bits architectures. The problem was the for unpack the source pointer was cast to a
specific type (uint32_t for 32 bits data) and then hton* was applied. The result was ... unexpected.
This patch always memcpy the data in a temporary variable with the correct size before calling
ntoh* functions, so we can insure that the data is always correctly aligned.
Moreover I add a debuging layer. OMPI_OUTPUT is used to print out the data being packed and
unpacked. It generate a lot of output but hopefully allow us to spot few bugs. This layer is not
completed the output stream descriptor is set to -1 (no output).
This commit was SVN r5617.
Anyway now I'm able to run on several 64 bits architectures (Athlon and G5) so
I suppose that we are back online on 64 bits.
This commit was SVN r5616.
everything in one directory. Still have only one Makefile, so it shouldn't
change build time at all
* Now that I finally understand the header system for data, refactor a little
bit of the code to match what really should be happening
* start of a hacked up send() - puts the data for a 0 byte message on the
other side, and all the pointers are where i think they should be. So
my plan of attack will work. But I think I'm going to have to use
iovecs instead of memcpy() real soon now.
This commit was SVN r5610.
one is selected it will be used for all purposes: small messages and long messages (even if the
long message is still split in several fragments). For the case where 2 PTLs per peer exists,
the first one is for latency (small messages and rendez-vous requests) when the second one
will be used for bandwitdh.
This commit was SVN r5600.
Jeff send me the way to do that automatically, and I'm pretty sure I'm not the only one who miss some
of the functionalities of our build system. The idea is really cool, let only the developper of a
component have it active until it reach a stable state. For all others peoples the .ompi_ignore
file prevent them for compiling the component.
cd src/mca/pml/uniq
echo $USER > .ompi_unignore
svn add .ompi_unignore
svn ci .ompi_unignore
This commit was SVN r5595.
for the size. If it does not fit, purge from the list, i.e. reset all
values to zero.
Fixes pgf90 problem, which silently accepts INTEGER*16, but internally
using INTEGER...
This commit was SVN r5594.
The idea behind this PML is to minimiza the overhead of managing multiple PTL. For each node, UNIQ keep two PTL's
one for latency and one for bandwidth. One the next version I want to add a configure parameter to allow the user
to select how many PTL's he want: one or two.
This commit was SVN r5593.