iscsi_tcp_segment_map(9)

💅 iscsi_tcp_segment_map — a kernel API moment (manual page iscsi_tcp_segment_map(9), yes bestie that's the whole title)

okay so picture this: you're deep in the kernel, the iscsi_tcp vibes are immaculate, and somebody has to map the current S/G page. That's this function. That's the whole gig. 🦋

---

✨ NAME ✨

iscsi_tcp_segment_map — map the current S/G page

Like, literally just that. It maps the current scatter/gather page. No cap. 💅

---

🌸 SYNOPSIS 🌸

void iscsi_tcp_segment_map (struct iscsi_segment *segment , int recv );

returns nothing (void), takes two things, moves on with its life. periodt. ✨

---

🎀 ARGUMENTS 🎀

• segment — an iscsi_segment. It's the segment. It's the whole point. 🫶
• recv — pass 1 if you're calling from the recv path. That's it, that's the flag. iykyk.

---

🔥 DESCRIPTION 🔥

Okay so here's the tea: we only need to possibly kmap data if scatter lists are being used. Why? Because the iscsi passthrough and internal IO paths will never use high mem pages. Never ever. Not once. So like... no need to be dramatic about it. 💀

So if scatter lists are in play, that's when this function does its little kmap thing. If not — nothing to do, we're chilling. 🌈

ngl this is one of those "small function, very specific job" situations. Respect it. 👑

---

🌟 SEE ALSO 🌟

Kernel file ./drivers/scsi/libiscsi_tcp.c and, like, the entire friend group:

• iscsi_tcp_segment_init_sg(9)
• iscsi_tcp_segment_done(9)
• iscsi_tcp_segment_recv(9)
• iscsi_tcp_hdr_recv_prep(9)
• iscsi_tcp_cleanup_task(9)
• iscsi_tcp_data_in(9)
• iscsi_tcp_r2t_rsp(9)
• iscsi_tcp_hdr_dissect(9)
• iscsi_tcp_hdr_recv_done(9)
• iscsi_tcp_recv_segment_is_hdr(9)
• iscsi_tcp_recv_skb(9)
• iscsi_tcp_task_init(9)
• iscsi_tcp_task_xmit(9)

go read them, they're all iconic in their own way. 🧚⭐

---

okay that's the page!! it lives in ./drivers/scsi, it's dated October 2026, and it's filed under iscsi_tcp_segment_map(9) — manual page iscsi_tcp_segment_map(9), obviously. mwah 💖 slay, go map some pages bestie 🎀