package ChakraProtoMsg

Get desktop application:
View/edit binary Protocol Buffers messages

Used in: GlobalMetadata, Node

• string name = 1

• string doc_string = 2

• oneof value

  • double double_val = 3

  • DoubleList double_list = 4

  • float float_val = 5

  • FloatList float_list = 6

  • int32 int32_val = 7

  • Int32List int32_list = 8

  • int64 int64_val = 9

  • Int64List int64_list = 10

  • uint32 uint32_val = 11

  • Uint32List uint32_list = 12

  • uint64 uint64_val = 13

  • Uint64List uint64_list = 14

  • sint32 sint32_val = 15

  • Sint32List sint32_list = 16

  • sint64 sint64_val = 17

  • Sint64List sint64_list = 18

  • fixed32 fixed32_val = 19

  • Fixed32List fixed32_list = 20

  • fixed64 fixed64_val = 21

  • Fixed64List fixed64_list = 22

  • sfixed32 sfixed32_val = 23

  • Sfixed32List sfixed32_list = 24

  • sfixed64 sfixed64_val = 25

  • Sfixed64List sfixed64_list = 26

  • bool bool_val = 27

  • BoolList bool_list = 28

  • string string_val = 29

  • StringList string_list = 30

  • bytes bytes_val = 31

  • BytesList bytes_list = 32

Block-layer operation (bio / request). Scope: limited to block-layer ops synchronously caused by an in-scope FS syscall via the page layer. Reads (page-cache-miss driven), writes (writeback driven by fsync/fdatasync/sync_file_range), and device cache flushes are in scope. Discard, secure erase, write-zeroes, and zone management originate from filesystem maintenance (trim, fstrim, fallocate) or zoned-storage management, not from the in-scope FS syscalls, and are intentionally excluded. References: - Linux block layer documentation: https://www.kernel.org/doc/html/latest/block/index.html - blk-mq / multi-queue block layer: https://www.kernel.org/doc/html/latest/block/blk-mq.html - REQ_OP_* definitions (include/linux/blk_types.h): https://elixir.bootlin.com/linux/latest/source/include/linux/blk_types.h - Tracepoint definitions (block lifecycle events Q/G/I/D/C): https://elixir.bootlin.com/linux/latest/source/include/trace/events/block.h - Runtime introspection on a live kernel: /sys/kernel/debug/tracing/events/block/*/format - blktrace event semantics (Q/G/I/D/C action identifiers): https://man7.org/linux/man-pages/man8/blktrace.8.html

Used in: StorageInfo

• BlockOp.OpType op = 1

  Producers populate whichever of lba / nr_sectors / req_op_flags their chosen tracepoint provides; for FLUSH ops, expect nr_sectors == 0 and lba == 0 since flushes carry no data payload.

• BlockOp.QueueEvent queue_event = 2

• string device = 3

• uint64 lba = 4

  logical block address (in sectors)

• uint32 nr_sectors = 5

• uint32 req_op_flags = 6

  REQ_* flags (REQ_SYNC, REQ_FUA, ...)

Mirrors REQ_OP_* in include/linux/blk_types.h. The op type is carried by every block lifecycle tracepoint (bi_opf & REQ_OP_MASK on the bio); it is not itself a distinct tracepoint.

Used in: BlockOp

• BLOCK_OP_UNKNOWN = 0

• BLOCK_OP_READ = 1

  REQ_OP_READ — issued on page-cache miss inside read/pread

• BLOCK_OP_WRITE = 2

  REQ_OP_WRITE — issued by writeback (caused by fsync/fdatasync/sync_file_range)

• BLOCK_OP_FLUSH = 3

  REQ_OP_FLUSH — device cache flush (caused by fsync/fdatasync)

Request lifecycle event at which this node was observed. See blktrace(8) and include/trace/events/block.h.

Used in: BlockOp

• BLOCK_EVENT_UNKNOWN = 0

• BLOCK_EVENT_QUEUE = 1

  Q — tracepoint: block:block_bio_queue (bio submitted via submit_bio)

• BLOCK_EVENT_GET = 2

  G — tracepoint: block:block_getrq (request struct allocated)

• BLOCK_EVENT_INSERT = 3

  I — tracepoint: block:block_rq_insert (added to scheduler queue)

• BLOCK_EVENT_DISPATCH = 4

  D — tracepoint: block:block_rq_issue (handed to driver)

• BLOCK_EVENT_COMPLETE = 5

  C — tracepoint: block:block_rq_complete (completion received)

Used in: AttributeProto

• repeated bool values = 1

Used in: AttributeProto

• repeated bytes values = 1

• ALL_REDUCE = 0

• REDUCE = 1

• ALL_GATHER = 2

• GATHER = 3

• SCATTER = 4

• BROADCAST = 5

• ALL_TO_ALL = 6

• REDUCE_SCATTER = 7

• REDUCE_SCATTER_BLOCK = 8

• BARRIER = 9

Used in: Node

• DATA_OP_UNKNOWN = 0

• DATA_OP_DATALOADER = 1

• DATA_OP_CHECKPOINT = 2

• DATA_OP_KV_TRANSFER = 3

Used in: AttributeProto

• repeated double values = 1

Used in: AttributeProto

• repeated fixed32 values = 1

Used in: AttributeProto

• repeated fixed64 values = 1

Used in: AttributeProto

• repeated float values = 1

Used in: StorageInfo

• FsOp.OpType op = 1

• string pathname = 2

• int32 fd = 3

• uint64 offset = 4

  byte offset within the file

• uint64 size_bytes = 5

  bytes requested / transferred

• uint32 flags = 6

Used in: FsOp

• FS_OP_UNKNOWN = 0

• FS_OP_OPEN = 1

• FS_OP_CLOSE = 2

• FS_OP_READ = 3

• FS_OP_WRITE = 4

• FS_OP_PREAD = 5

• FS_OP_PWRITE = 6

• FS_OP_FSYNC = 7

  flush file's dirty data + metadata to device

• FS_OP_FDATASYNC = 8

  flush dirty data (+ metadata only if needed for retrieval)

• FS_OP_SYNC_FILE_RANGE = 9

  flush a specified byte range of dirty data to device

• string version = 1

• repeated AttributeProto attr = 2

Used in: Node

• string values = 1

• string shapes = 2

• string types = 3

Used in: AttributeProto

• repeated int32 values = 1

Used in: AttributeProto

• repeated int64 values = 1

• uint64 id = 1

• string name = 2

• NodeType type = 3

• repeated uint64 ctrl_deps = 4

  Control and data dependencies

• repeated uint64 data_deps = 5

• uint64 start_time_micros = 6

  Timing information

• uint64 duration_micros = 7

• optional IOInfo inputs = 8

• optional IOInfo outputs = 9

• repeated AttributeProto attr = 10

• oneof op_info

  Type-specific info.

  • StorageInfo storage = 11

    type == STORAGE_NODE

  • DataOpType data_op = 12

    type == DATA_OP_NODE

Used in: Node

• INVALID_NODE = 0

• METADATA_NODE = 1

• MEM_LOAD_NODE = 2

• MEM_STORE_NODE = 3

• COMP_NODE = 4

• COMM_SEND_NODE = 5

• COMM_RECV_NODE = 6

• COMM_COLL_NODE = 7

• STORAGE_NODE = 8

• DATA_OP_NODE = 9

Page-cache operation. Scope: limited to page-cache events that are synchronously caused by an in-scope FS syscall and that can be causally attributed back to that syscall. Background-only events (eviction outside truncate, memory-pressure reclaim) and events with no FS syscall upstream (mmap page faults) are intentionally excluded. References: - Linux memory management concepts (page cache, writeback): https://www.kernel.org/doc/html/latest/admin-guide/mm/concepts.html - Tracepoint definitions (authoritative names, fields, print formats): filemap: https://elixir.bootlin.com/linux/latest/source/include/trace/events/filemap.h writeback: https://elixir.bootlin.com/linux/latest/source/include/trace/events/writeback.h - Runtime introspection on a live kernel: /sys/kernel/debug/tracing/events/{filemap,writeback}/*/format - Readahead kprobe targets (no dedicated tracepoint; kprobed directly): page_cache_sync_ra: https://elixir.bootlin.com/linux/latest/A/ident/page_cache_sync_ra page_cache_async_ra: https://elixir.bootlin.com/linux/latest/A/ident/page_cache_async_ra

Used in: StorageInfo

• PageOp.OpType op = 1

  Producers populate whichever of inode / page_index / nr_pages their chosen tracepoint provides.

• uint64 inode = 2

  backing inode when applicable

• uint64 page_index = 3

  page offset within the file (PAGE_SIZE units)

• uint32 nr_pages = 4

  number of contiguous pages affected

Used in: PageOp

• PAGE_OP_UNKNOWN = 0

• PAGE_OP_ADD_TO_CACHE = 1

  tracepoint: filemap:mm_filemap_add_to_page_cache

• PAGE_OP_DIRTY = 2

  tracepoint: writeback:writeback_dirty_folio

• PAGE_OP_READAHEAD_SYNC = 3

  Two readahead variants distinguished by who triggered them. SYNC: cache-miss-driven during a read syscall — the user needs these pages now, the kernel widens the request to also prefetch ahead.

  kprobe: page_cache_sync_ra

• PAGE_OP_READAHEAD_ASYNC = 6

  ASYNC: tripwire-driven follow-up — a previous readahead marked a page with PG_readahead; when the user touches that page, the kernel kicks off the next prefetch without blocking the user.

  kprobe: page_cache_async_ra

Used in: AttributeProto

• repeated sfixed32 values = 1

Used in: AttributeProto

• repeated sfixed64 values = 1

Used in: AttributeProto

• repeated sint32 values = 1

Used in: AttributeProto

• repeated sint64 values = 1

Used in: Node

• StorageLevel level = 1

• oneof detail

  • FsOp fs = 10

  • PageOp page = 11

  • BlockOp block = 12

    STORAGE_LEVEL_DEVICE: no typed detail — use Node.attr.

Layer within the storage stack at which the operation is observed.

Used in: StorageInfo

• STORAGE_LEVEL_UNKNOWN = 0

• STORAGE_LEVEL_FS = 1

  VFS / filesystem syscalls

• STORAGE_LEVEL_PAGE = 2

  page cache / mm

• STORAGE_LEVEL_BLOCK = 3

  block layer (bio / request)

• STORAGE_LEVEL_DEVICE = 4

  device transport (NVMe/SCSI/ATA) and below; typed schema intentionally omitted

Used in: AttributeProto

• repeated string values = 1

• uint64 tensor_id = 1

  An unique ID for the TensorImpl object.

• uint64 storage_id = 2

  An unique ID for the underlying storage object.

• uint64 offset = 3

  Offset to the storage memory.

• uint64 num_elem = 4

  Number of elements in the storage.

• uint64 elem_bytes = 5

  Number of bytes per element.

• string device = 6

  Tensor object device location.

Used in: AttributeProto

• repeated uint32 values = 1

Used in: AttributeProto

• repeated uint64 values = 1