iucv_register(9)
β¨ NAME β¨
iucv_register β registers a driver with IUCV. This is the iucv_register(9) page from the Kernel API Manual, and yes bestie, we're getting your driver hooked up to IUCV. π
πΈ SYNOPSIS πΈ
int iucv_register (struct iucv_handler *handler , int smp );
π ARGUMENTS π
handlerβ the address of the iucv handler structure. Like, where your handler lives, hand it over. π«Άsmpβ!= 0indicates that the handler can deal with out of order messages. No cap, that's literally what it means. π
π RETURN π
0on success β periodt. β¨-ENOMEMif the memory allocation for the pathid table failed. π-EIOifIUCV_DECLARE_BUFFERfailed on all cpus. π
π¦ SEE ALSO π¦
Kernel file ./net/iucv/iucv.c and the whole friend group: __iucv_call_b2f0(9), iucv_allow_cpu(9), iucv_block_cpu(9), iucv_declare_cpu(9), iucv_retrieve_cpu(9), iucv_sever_pathid(9), __iucv_cleanup_queue(9), iucv_cleanup_queue(9), iucv_unregister(9), iucv_path_accept(9), iucv_path_connect(9), iucv_path_quiesce(9), iucv_path_resume(9), iucv_path_sever(9), iucv_message_purge(9), iucv_message_receive_iprmdata(9), __iucv_message_receive(9), iucv_message_receive(9), iucv_message_reject(9), iucv_message_reply(9), __iucv_message_send(9), iucv_message_send(9), iucv_message_send2way(9), iucv_path_pending(9), iucv_path_complete(9), iucv_path_severed(9), iucv_path_quiesced(9), iucv_path_resumed(9), iucv_message_complete(9), iucv_message_pending(9), iucv_init(9), iucv_exit(9).
Okay so this whole page is from ./net/iucv, dated October 2026 β mwah π, go be the main character of kernel networking. π
π¦ 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