charm AT lists.cs.illinois.edu

Subject: Charm++ parallel programming system

List archive

Re: [charm] [ppl] CmiFopen() and CmiFwrite() from C

From: Phil Miller <mille121 AT illinois.edu>
To: Tom Quinn <trq AT astro.washington.edu>
Cc: "charm AT cs.illinois.edu" <charm AT cs.illinois.edu>, "cosmology-ppl AT cs.uiuc.edu" <cosmology-ppl AT cs.uiuc.edu>
Subject: Re: [charm] [ppl] CmiFopen() and CmiFwrite() from C
Date: Thu, 27 Dec 2012 14:25:47 -0600
List-archive: <http://lists.cs.uiuc.edu/pipermail/charm/>
List-id: CHARM parallel programming system <charm.cs.uiuc.edu>

On Thu, Dec 27, 2012 at 1:33 PM, Phil Miller
<mille121 AT illinois.edu>
wrote:
> On Thu, Dec 27, 2012 at 1:21 PM, Tom Quinn
> <trq AT astro.washington.edu>
> wrote:
>> What with Lustre becoming more common, and its habit of failing with
>> "EINTR", could the CmiFopen, CmiFwrite, and CmiFclose (and there probably
>> needs to be a CmiFread), which handle this case, be made available to "C"
>> code as well as C++? I think all that needs to be done is add an 'extern
>> "C"' in front of the declarations in converse.h and the definitions in
>> util/pup_util.C.
>
> That all sounds reasonable to me. I'll have it pushed in a couple minutes.

The exposure of the 3 existing functions to C code is done. I'm
actually a bit curious to see why there's no matching read call, since
that can certainly be interrupted. I'll follow up on this.

[charm] CmiFopen() and CmiFwrite() from C, Tom Quinn, 12/27/2012
- Re: [charm] [ppl] CmiFopen() and CmiFwrite() from C, Phil Miller, 12/27/2012
  - Re: [charm] [ppl] CmiFopen() and CmiFwrite() from C, Phil Miller, 12/27/2012
    - Re: [charm] [ppl] CmiFopen() and CmiFwrite() from C, Tom Quinn, 12/27/2012