Function __encode_userdata

examples/proxy.h:33–43

* Packs the information that we will need at completion time into the * sqe->user_data field, which is passed back in the completion in * cqe->user_data. Some apps would need more space than this, and in fact * I'd love to pack the requested IO size in here, and it's not uncommon to * see apps use this field as just a cookie to either index a data structure * at completion time, or even just

 * structure into this field.
 */
static inline void __encode_userdata(struct io_uring_sqe *sqe, int tid, int op,
				     int bid, int fd)
{
	struct userdata ud = {
		.op_tid = (op << OP_SHIFT) | tid,
		.bid = bid,
		.fd = fd
	};

	io_uring_sqe_set_data64(sqe, ud.val);
}

static inline uint64_t __raw_encode(int tid, int op, int bid, int fd)
{