{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreie7xohxs75q4kqrhzfuoann72bylehaxntkcvkyi5wydt2dl6lkcq",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mk722ztwfmr2"
  },
  "path": "/t/pre-rfc-btf-relocations/24161#post_19",
  "publishedAt": "2026-04-23T21:28:59.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "It's actually quite common to have `task->se.vruntime` accesses in C BPF programs, so supporting this from the get go would be essential to make this useful for real-world applications.\n\nRe: naming. \"preserve_access_index\" naming we use in C is quite opaque and not very meaningful. Everyone just remembered and use it without asking questions, but I always felt like having it named as \"btf_relocatable\" or something along those lines (\"relocatable\" is the key here, IMO) would be best. Just my 2 cents on naming.",
  "title": "[Pre-RFC] BTF relocations"
}