Project

General

Profile

Feature #177

Feature #108: Fixed-size object IDs

objid_t: load balancing infrastructure should use objid_t

Added by Ramprasad Venkataraman over 6 years ago. Updated 4 months ago.

Status:
In Progress
Priority:
Low
Assignee:
Category:
Load Balancing
Target version:
Start date:
04/09/2013
Due date:
% Done:

0%


Description

Once the basic objid_t scaffolding is available (#170), the impacts on the LB infrastructure and strategies should be audited. Specifically, the load balancing database, ldb calls on the message send and delivery paths might only have an objid_t available at that point in the code. For eg look at idx2LDobjid(). Hence, the benefits of managing all the LDB using objid_t should be evaluated / discussed. Implementation decisions should be made accordingly.

One observation is that the presence of an inversion function to obtain array index from objid_t may provide the extra data that user code has to provide to some LB strategies.


Related issues

Related to Charm++ - Cleanup #1422: Cleanup dangling issues from 64bit merge In Progress 02/15/2017

History

#1 Updated by Phil Miller almost 6 years ago

  • Target version changed from 6.6.0 to 6.7.0

This won't be ready for 6.6, so push it back.

#2 Updated by Phil Miller almost 4 years ago

  • Target version changed from 6.7.0 to 6.8.0

#3 Updated by Phil Miller almost 3 years ago

  • Assignee changed from Harshitha Menon to Kavitha Chandrasekar

#4 Updated by Sam White over 2 years ago

  • Category set to Load Balancing

#5 Updated by Phil Miller about 2 years ago

  • Target version changed from 6.8.0 to 6.9.0

#6 Updated by Kavitha Chandrasekar over 1 year ago

  • Status changed from New to In Progress

#7 Updated by Sam White about 1 year ago

This needs to be discussed in Core as to whether we should break the API that NAMD is suing or defer to a later release.

#8 Updated by Juan Galvez 12 months ago

  • Status changed from In Progress to Implemented

#9 Updated by Sam White 11 months ago

  • Status changed from Implemented to Merged

#10 Updated by Eric Mikida 4 months ago

  • Status changed from Merged to In Progress
  • Assignee changed from Kavitha Chandrasekar to Eric Mikida
  • Priority changed from Normal to Low
  • Target version changed from 6.9.0 to Unscheduled

Reopening and reassigning this because the patch maybe didn't fully address the issue. It uses a combination of 64bit ID, and Location manager ID. Worth evaluating whether we can do better.

#11 Updated by Eric Mikida 4 months ago

  • Related to Cleanup #1422: Cleanup dangling issues from 64bit merge added

Also available in: Atom PDF