From: Thomas Fischbacher <tf@functionality.de>
To: Caml-list List <caml-list@inria.fr>
Subject: CamlMPI: sending marshalled objects
Date: Tue, 22 Jan 2008 18:52:28 +0000 [thread overview]
Message-ID: <47963B6C.1010301@functionality.de> (raw)
Hello everybody,
there is an old Caml/MPI interface, written by Xavier himself in 1998.
This provides a pair of C functions caml_mpi_send/caml_mpi_receive,
which may look a bit funny considering present day ML-C-interface coding
conventions, but GC-wise is actually valid code as far as I can judge.
For reference, I added them at the end of this email.
As far as I can see, output_value_to_malloc() actually should be able to
serialize virtually any ML object (which does not contain alloc_custom()
blocks and similar stuff) to a buffer. Sending this over the net also
should not be much of a problem, regardless of the data being sent. If,
on the other hand, I manually serialized to a string and tried to send
that, I would be bound by the 16 MB maximal string length limitation on
32-bit architectures.
So much the theory. But what I actually find in reality is that -- even
using caml_mpi_send/caml_mpi_receive rather than intermediate strings --
my code crashes when I try to pass around serialized ML data over MPI
which is larger than 16 MB. I am not yet 100% sure that this really is
the problem, but at present, I have every reason to believe so.
So, (1) what is going on here, and (2) how can I repair it?
Is there a quick fix?
value caml_mpi_send(value data, value flags,
value dest, value tag, value vcomm)
{
MPI_Comm comm = Comm_val(vcomm);
char * buffer;
long len;
Begin_root(vcomm) /* prevent deallocation of communicator */
output_value_to_malloc(data, flags, &buffer, &len);
/* This also allocates the buffer */
enter_blocking_section();
MPI_Send(buffer, len, MPI_BYTE, Int_val(dest), Int_val(tag), comm);
leave_blocking_section();
End_roots();
stat_free(buffer);
return Int_val(len);
}
value caml_mpi_receive(value vlen, value source, value tag, value vcomm)
{
MPI_Comm comm = Comm_val(vcomm);
mlsize_t len = Long_val(vlen);
char * buffer;
MPI_Status status;
value res;
Begin_root(vcomm) /* prevent deallocation of communicator */
buffer = stat_alloc(len);
enter_blocking_section();
MPI_Recv(buffer, len, MPI_BYTE,
Int_val(source), Int_val(tag), comm, &status);
leave_blocking_section();
res = input_value_from_malloc(buffer, 0);
/* This also deallocates the buffer */
End_roots();
return res;
}
--
best regards,
Thomas Fischbacher
t.fischbacher@soton.ac.uk
next reply other threads:[~2008-01-22 18:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 18:52 Thomas Fischbacher [this message]
2008-01-23 10:15 ` [Caml-list] " Olivier Andrieu
2008-01-23 11:52 ` Thomas Fischbacher
2008-01-23 11:48 ` Jon Harrop
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47963B6C.1010301@functionality.de \
--to=tf@functionality.de \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox