Charm++ parallel programming system

[Lukasz Wesolowski <wesolwsk AT illinois.edu>]

Yes, that's the one.

Lukasz

On Fri, Sep 13, 2013 at 4:23 PM, Rafael Keller Tesser
<rktesser AT inf.ufrgs.br>
 wrote:
> Thanks Lukasz.
>
> I didn't remember to look for it in the repository.
> I assume the GPU Manager you referred to is the one under
> src/arch/cuda/hybridAPI. Is that right?
>
> --
> Rafael Keller Tesser
> GPPD-UFRGS
>
>
> On Thu, Sep 12, 2013 at 5:19 PM, Lukasz Wesolowski 
> <wesolwsk AT illinois.edu>
> wrote:
>>
>> Hi Rafael,
>>
>> We have a low-level task library (GPU Manager, previously called
>> Hybrid API) for encapsulating and offloading work to CUDA-based GPUs.
>> We also have the higher-level Accelerated Entry Method framework,
>> built on top of GPU Manager, that generates CUDA kernels from
>> appropriately tagged entry methods and controls for grain size by
>> batching or splitting the work from instances of these methods
>> belonging to different chares. These tools are available in the charm
>> repository. GPU Manager is in active use while the AEM framework may
>> be a little rusty.
>>
>> In addition, there is G-Charm, also built on top of GPU Manager, which
>> is an externally developed library for agglomerating and scheduling
>> GPU work and optimizing for data reuse.
>>
>> Lukasz
>>
>> On Thu, Sep 12, 2013 at 2:18 PM, Rafael Keller Tesser
>> <rktesser AT inf.ufrgs.br>
>>  wrote:
>> > Hello!
>> >
>> > I'd like to know what's the current state of GPU support in Charm++.
>> > I've
>> > read some publications on the subject but the tools (or libraries) that
>> > have
>> > been used in these works don't seem to be available to the general
>> > public.
>> >
>> > --
>> > Best regards,
>> >         Rafael Keller Tesser
>> >         GPPD-UFRGS
>> >
>> > _______________________________________________
>> > charm mailing list
>> > charm AT cs.uiuc.edu
>> > http://lists.cs.uiuc.edu/mailman/listinfo/charm
>> >
>
>
>
>
> --
>
>         Rafael Keller Tesser