diag_cmd_data_alloc(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME

Okay bestie, you’ve landed on diag_cmd_data_alloc(9) from the Kernel API Manual β€” and its whole thing is that it fills in a bde struct with dma buffers. Iconic, honestly. ✨


πŸ¦‹ SYNOPSIS

struct lpfc_dmabufext * diag_cmd_data_alloc (struct lpfc_hba *phba ,
struct ulp_bde64 *bpl , uint32_t size , int nocopydata );

πŸŽ€ ARGUMENTS

  • phba β€” Pointer to HBA context object.
  • bpl β€” Pointer to 64 bit bde structure.
  • size β€” Number of bytes to process.
  • nocopydata β€” The flag to copy user data into the allocated buffer.

🌸 DESCRIPTION

This function is doing the absolute most: it allocates page size buffers and populates an lpfc_dmabufext. 🫢

If allowed, the user data pointed to with indataptr is copied into the kernel memory. Then the chained list of page size buffers is returned. No cap, that’s the whole flow. πŸ’…


πŸ‘‘ SEE ALSO


Okay bye bestie β€” this page lives in ./drivers/scsi/lpfc, it’s dated October 2026, and it’s filed under diag_cmd_data_alloc(9). Mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from