iucv_register(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ 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 β€” != 0 indicates that the handler can deal with out of order messages. No cap, that's literally what it means. πŸ’…

πŸ’– RETURN πŸ’–

  • 0 on success β€” periodt. ✨
  • -ENOMEM if the memory allocation for the pathid table failed. 😭
  • -EIO if IUCV_DECLARE_BUFFER failed 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