Skip to content

tags can exceed 32 bits #7

@matt-dbs

Description

@matt-dbs

GOAL appears to have two formats, binary and textual. Both the binary format and in-memory data structures represent DeserializedNode.Tag as a 32-bit unsigned integer. However the GOAL textual format appears to support tags >32-bit. E.g.:

  1. http://storage2.spcl.ethz.ch/traces/ai/llama/Llama7B_N4_GPU16_TP1_PP1_DP16_BS32/llama.goal
  2. http://storage2.spcl.ethz.ch/traces/ai/llama/Llama7B_N4_GPU16_TP1_PP1_DP16_BS32/llama.bin

Line 7176456 of (1) has:

l100000: recv 788480b from 0 tag 21020814305 cpu 4 nic 0

but if you parse and interpret (2), you find this entry has the tag 3840945121. 3840945121 = 21020814305 & (2³² - 1). Maybe the GOAL binary format is intended to use a 64-bit tag field?

I’m basically reverse engineering here, so please let me know if I’ve mistaken something.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions