caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Ohad Rodeh" <ORODEH@il.ibm.com>
To: <Horus-l@cornell.edu>, caml-announce@inria.fr
Subject: [Caml-list] Ensemble version 1.40 released
Date: Thu, 19 Dec 2002 10:42:10 +0200	[thread overview]
Message-ID: <OF332AAC9B.7310BBE3-ONC2256C94.002F80E5-C2256C94.002FCEA4@telaviv.ibm.com> (raw)

List,
   A new release is now available from the system homepage at www.cs.cornell.edu/Info/Projects/Ensemble,
enjoy!


  RELEASE_NOTES for Ensemble version 1.40

Author: Ohad Rodeh
Last updated: 19/December/2002

RELEASE_NOTES

  This release primarily solves a long standing problem with the use
of DLLs on win32 platforms. CE was rewritten so as to compiled into a
DLL instead of a static library. Since JNI requires shared libraries,
this finally allows cejava to work on win32 and not just Unix. The second
problem solved in this release is the gossip bug on win32, this was due
to problems with UDP sockets.

The major change in the CE API is in memory allocation
conventions. Instead of the application allocating memory chunks, such
as arrays of destinations and vectors pointing to C-memory chunks, CE
now copies these auxiliary buffers into its own memory areas. This
completely separates the memory areas used by the application and
CE/Ensemble. The only sharing occurs for message bodies which are not
copied. To this end the application must set the message alloc/free
functions used by CE for messages, for example:

    ce_set_alloc_fun((mm_alloc_t)malloc);
    ce_set_free_fun((mm_free_t)free);

will allows messages allocated by the application using malloc to freed by Ensemble.

The API change would require CE applications to be modified for the
new memory conventions, which is not a "good thing". This was done
primarily to allow using DLLs, where each DLL keeps a private copy of
LIBC. Therefore, memory allocated by one DLL (the application) cannot be
freed by another DLL (CE). In the longer term, it separates the
application and library from each other and should make developement
easier. It also saves allocations for iovector arrays and destination arrays on
the critical message send path.

OCAML COMPILER VERSION
  We are using version 3.06 for this version.

PORTABILITY
  This version was tested on Linux (RedHat 7.1, 7.2, 7.3, i386 architecture) and windows XP.


-----------------------------------------------------------------------------------

Ohad Rodeh
tel: +972-3-6401641
IBM Haifa, storage research

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


             reply	other threads:[~2002-12-19  8:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-19  8:42 Ohad Rodeh [this message]
2002-12-19 14:52 ` [Caml-list] lablGL + cygwin Christophe Raffalli
     [not found]   ` <Pine.LNX.4.50.0212200051070.6076-100000@home.oyster.ru>
2002-12-20 12:38     ` Christophe Raffalli
2002-12-20  9:27 ` [Caml-list] Ensemble version 1.40 released Mike Potanin
2002-12-20 13:01   ` Mike Potanin
2002-12-20 17:26     ` Ohad Rodeh

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=OF332AAC9B.7310BBE3-ONC2256C94.002F80E5-C2256C94.002FCEA4@telaviv.ibm.com \
    --to=orodeh@il.ibm.com \
    --cc=Horus-l@cornell.edu \
    --cc=caml-announce@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;
as well as URLs for NNTP newsgroup(s).