charm AT lists.siebelschool.illinois.edu
Subject: Charm++ parallel programming system
List archive
- From: Eric Mikida <epmikida AT hpccharm.com>
- To: charm AT lists.cs.illinois.edu
- Subject: [charm] Array Maps in Charm++
- Date: Thu, 16 Apr 2020 14:17:32 -0400
- Authentication-results: illinois.edu; spf=none smtp.mailfrom=epmikida AT hpccharm.com; dkim=pass header.d=hpccharm-com.20150623.gappssmtp.com header.s=20150623; dmarc=none
Some recent issues have cropped up related to array maps in Charm++ that has
led us to start re-evaluating the current API and usage of array maps. Before
diving in though, I had a couple of questions for array developers:
1) Do you use any built-in Charm maps other than the default array map?
2) Does your application define it’s own array maps?
2b) If you define your own maps, do your maps define and use their own
entry methods?
2c) Do you use a single map instance to manage multiple chare arrays in a
non-trivial way?
Right now the plan is to clean up the API and how the maps are instantiated,
which probably will also involve change maps from group chares to just
regular C++ objects.
Thanks
Eric
- [charm] Array Maps in Charm++, Eric Mikida, 04/16/2020
Archive powered by MHonArc 2.6.19.