QB_IPCC_SENDV(3)

πŸ’– qb_ipcc_sendv β€” from the libqb Programmer's Manual (section 3) πŸŽ€

okay bestie, gather round, because this one is short and sweet but it's load-bearing. qb_ipcc_sendv is the "send a message, but with iovecs" girlie. Scatter-gather energy. Periodt. ✨


✨ NAME ✨

qb_ipcc_sendv β€” Send a message (iovec).


✨ SYNOPSIS ✨

#include <qb/qbipcc.h>

ssize_t qb_ipcc_sendv(
    qb_ipcc_connection_t   *c,        /* connection instance */
    const struct iovec     *iov,      /* pointer to an iovec struct to send */
    size_t                  iov_len   /* the number of iovecs used */
);

✨ PARAMS ✨

  • c β€” the connection instance, aka your whole entire situationship with the server 🫢
  • iov β€” pointer to an iovec struct you wanna send πŸ’Œ
  • iov_len β€” how many iovecs you're actually using πŸ‘‘

✨ DESCRIPTION ✨

ngl, the original page just… leaves this section blank. Not a single word. The silence is giving mysterious main character energy 😭✨ but fr fr, there's nothing here to tell you, so I'm not about to make stuff up. Scroll down to NOTE, that's where the real tea is πŸ“


✨ RETURN VALUE ✨

(size sent, -errno == error)

So like β€” it hands you back the number of bytes sent, and if things go sideways you get -errno instead. A negative number here is not a vibe check you passed, bestie πŸ’€


✨ NOTE ✨

🚨 listen up, this is the important one: iov[0] must be a qb_ipc_request_header. The server is gonna read the size field to figure out how much to recv. No header in slot zero, no message. It's giving strict, but that's just how it is πŸ’…

✨ SEE ALSO ✨

your reading list, bestie, go be nosy πŸ‘‘πŸ“š


Copyright (C) 2010-2020 Red Hat, Inc. 🫢


and that's the whole page, no crumbs left 🌈 so like, credit where it's due: this is from the libqb programmer's manual, dated 2025-09-16. mwah, go send some iovecs responsibly, ily πŸ’œπŸ¦‹

πŸ“¦ where this page comes from