Charm++ parallel programming system

[Xuehan Xu <xxhdx1985126 AT gmail.com>]

Dear Sirs:
     I built the charm++ with the "version" set to "net-linux". It seemed that the charmrun.c file always includes the converse.h which in turn includes src/arch/net-linux/conv-mach.h, in which the macro CMK_SHARED_VARS_UNAVAILABLE is always defined as 1. Dose this mean that the shared variables are always not available when I run "./build charm++ net-linux"?
     I've also review several conv-mach.h files in other directory, such as src/arch/mpi-linux/conv-mach.h, they define CMK_SHARED_VARS_UNAVAILABLE as 1, too. Which version should I choose to use shared variables?

On 19 January 2011 00:31, Phil Miller <mille121 AT illinois.edu> wrote:

It means there won't be multiple PEs sharing virtual address space as
multiple threads in a common process. In other words, shared variables
are available on SMP and multicore builds of Charm, but not the
versions that fork a separate process per PE.

On Tue, Jan 18, 2011 at 10:12, Xuehan Xu <xxhdx1985126 AT gmail.com> wrote:
> Dear sirs:
>         I've been reviewing charm source code in the past few days, and I
> discovered "CMK_SHARED_VARS_UNAVAILABLE" is defined, then the field "cpus"
> of every element of the "nodetab_table" can only be 1, why is that? What
> does the macro "CMK_SHARED_VARS_UNAVAILABLE" mean?
>

> _______________________________________________
> ppl mailing list
> ppl AT cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/ppl
>
>