Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
C
codes
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 38
    • Issues 38
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 8
    • Merge Requests 8
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • codes
  • codes
  • Issues
  • #143

Closed
Open
Opened Mar 03, 2016 by Jonathan Jenkins@jenkins
  • Report abuse
  • New issue
Report abuse New issue

dragonfly - cache router LP-ID in terminal state

While investigating #142 (closed) an optimization opportunity came to mind. The number of codes-mapping calls in the dragonfly can be reduced by a significant amount by storing the router LP-ID in the terminal rather than the relative ID, which then must be re-calculated for each flit.

We could take this one step further by storing the full set of neighbor LP IDs, since the neighbors of any dragonfly entity are statically defined (could do this for any statically-defined network topology), but those changes would be more far-reaching.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: codes/codes#143