iscsi_sw_tcp_xmit_segment(9)

✨ iscsi_sw_tcp_xmit_segment ✨

okay so this is a page from the Kernel API Manual, bestie — it's iscsi_sw_tcp_xmit_segment(9) and it's genuinely iconic in a quiet, backend-driver way 🎀

---

🌸 NAME 🌸

iscsi_sw_tcp_xmit_segment — transmit segment 💅

---

🦋 SYNOPSIS 🦋

int iscsi_sw_tcp_xmit_segment (struct iscsi_tcp_conn *tcp_conn , struct
       iscsi_segment *segment );

like, it returns an int, takes two structs, slay ✨

---

💖 ARGUMENTS 💖

• tcp_conn — the iSCSI TCP connection 🫶 that's the whole vibe
• segment — the buffer to transmnit

ok so real talk, the original page literally spells it transmnit and I'm not about to lie to you — that's the word on the page 💀 it means the buffer you're sending, no cap

---

🔥 DESCRIPTION 🔥

So what this function does: it transmits as much of the buffer as the network layer will accept, and returns the number of bytes transmitted 🧚 that's it, that's the whole job, and it ate 💅

If CRC hashing is enabled, the function will compute the hash as it goes ⭐ like it's multitasking, main character energy tbh. And then — when the entire segment has been transmitted — it will retrieve the hash value and send it along as well 🎀 so the hash just hops on the ride at the end, obsessed 🌈

---

👑 SEE ALSO 👑

Kernel file ./drivers/scsi/iscsi_tcp.c — and also these besties, go say hi 🦋

• iscsi_sw_tcp_recv(9)
• iscsi_sw_sk_state_check(9)
• iscsi_sw_tcp_write_space(9)
• iscsi_sw_tcp_xmit(9)
• iscsi_sw_tcp_xmit_qlen(9)

---

ok that's the whole page, no notes 🙈 stay hydrated, read your kernel source, mwah 💜

signing off from ./drivers/scsi — October 2026 — this has been your girl, iscsi_sw_tcp_xmit_segment(9) 🎀✨