ibmvscsi_set_request_limit(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ibmvscsi_set_request_limit πŸ’…

okay so bestie, welcome to the ibmvscsi_set_request_limit(9) page from the Kernel API Manual ✨ β€” this is the little function that sets the adapter's request_limit when the adapter's having a Moment (failure, reset, or SRP Login) 🫢


✨ NAME ✨

ibmvscsi_set_request_limit β€” sets the adapter request_limit in response to an adapter failure, a reset, or an SRP Login πŸ’– and the whole thing runs under host lock, specifically so it doesn't race with SCSI command submission. no cap, that lock is the main character here πŸ‘‘


πŸ¦‹ SYNOPSIS πŸ¦‹

void ibmvscsi_set_request_limit (struct ibmvscsi_host_data *hostdata ,
int limit );

it returns void btw β€” nothing comes back, it just does the thing πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • hostdata β€” the adapter you're adjusting, like, the whole point 🧚
  • limit β€” the brand new request limit, the fresh number, the glow-up ⭐

🌈 SEE ALSO 🌈

the kernel file lives at ./drivers/scsi/ibmvscsi/ibmvscsi.c (iykyk) and honestly the friend group here is huge, so buckle up buttercup, here's everyone πŸ“:

like, go read all of them, they're literally all connected, it's giving one big happy driver family πŸ˜­πŸ’–


lowkey reminder: this thing touches request_limit and it does it under host lock β€” that's not decoration, that's the whole reason it's safe against SCSI command submission racing in. respect the lock πŸ™ˆ

and that's the page!! sourced from ./drivers/scsi/ibmvscsi 🌸 dated October 2026 πŸ’œ mwah, slay, go forth and set those request limits responsibly βœ¨πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from