hfi1_ud_rcv(9)
π hfi1_ud_rcv β like, the whole Kernel API Manual page, but make it make sense
Ok so bestie, welcome to the Kernel API Manual entry for hfi1_ud_rcv(9). Section 9, obviously β kernel developer vibes only. Let's get into it β¨
β¨ NAME β¨
hfi1_ud_rcv β the moment an incoming UD packet shows up and this function is literally right there to receive it π
πΈ SYNOPSIS πΈ
void hfi1_ud_rcv (struct hfi1_packet *packet );
That's it. That's the whole call. One pointer, no drama, no return value. Iconic minimalism honestly π
π¦ ARGUMENTS π¦
packetβ the packet structure. Like, the packet structure. The one and only thing you hand over π«Ά
π DESCRIPTION π
So here's the tea: this gets called from qp_rcv to process an incoming UD packet for the given QP. You're not the one kicking things off β qp_rcv is doing the intro, and hfi1_ud_rcv is the one actually handling the UD packet for that QP π
Heads up bestie: this is called at interrupt level. So likeβ¦ context matters, ok? Don't be out here doing sleep-y things. You're in interrupt land now π
π SEE ALSO π
- Kernel file
./drivers/infiniband/hw/hfi1/ud.cβ yeah, that's where the whole friend group lives ud_loopback(9)β¨hfi1_make_ud_req(9)β¨
π a lil sign-off π
That's the whole page, bestie! Source situation: ./drivers/infiniband/hw/hfi1, and the date stamp is October 2026. Go forth and receive those UD packets β you got this fr fr ππ§ββοΈ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms