STRUCT HMCDRV_CACHE_ENTRY(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– struct hmcdrv_cache_entry(9) πŸ’–

okay bestie, so this is a kernel API manual page for struct hmcdrv_cache_entry β€” it's literally the file cache struct and it's only used on read/dir operations, no cap. the manual name is struct hmcdrv_cache_entry(9) but we're just gonna vibe with the struct itself, periodt. ✨


πŸŽ€ SYNOPSIS πŸŽ€

struct hmcdrv_cache_entry {
    enum hmcdrv_ftp_cmdid id;
    char fname[HMCDRV_FTP_FIDENT_MAX];
    size_t fsize;
    loff_t ofs;
    unsigned long timeout;
    void *content;
    size_t len;
 };

πŸ¦‹ MEMBERS πŸ¦‹

  • id β€” the FTP command ID, slay πŸ’…
  • fname β€” the file name, iconic
  • fsize β€” the file size, noted 🫢
  • ofs β€” start of content within the file, and it's -1 if there's no cached content (so if you see a negative here, just know it's giving "nothing cached bestie" energy 😭)
  • timeout β€” the cache timeout in jiffies, lowkey important
  • content β€” kernel-space buffer that's 4k aligned, fancy ✨
  • len β€” size of the content cache, and it's 0 if caching is disabled (so zero means no caching, iykyk)

πŸ’œ DESCRIPTION πŸ’œ

okay so here's the tea β€” the first three members (id, fname, fsize) are cached on all read/dir requests. literally all of them. no skips. 🎯

but content? that's different. content is only cached under some preconditions, so not every time. the way that uncached content is signalled is by a negative value of ofs β€” so if ofs is negative, that's your sign that the content isn't cached. periodt. πŸ’€


🌈 SEE ALSO 🌈


alright bestie, that's the whole struct and all its members, no details left behind, we ate that up. πŸ“ the source is ./drivers/s390/char, the date is October 2026, and the version is struct hmcdrv_cache_entry(9) β€” catch you on the next manpage, mwah πŸ’‹πŸ‘‘

πŸ“¦ where this page comes from