From: Jens Axboe <axboe@kernel.dk>
To: Gabriel Krisman Bertazi <krisman@suse.de>
Cc: io-uring@vger.kernel.org
Subject: Re: [PATCH liburing 1/5] liburing: Add helper to prepare IORING_OP_BIND command
Date: Sun, 21 Jul 2024 15:18:09 -0600 [thread overview]
Message-ID: <403f0652-8f2d-400e-9f18-99b0b4085670@kernel.dk> (raw)
In-Reply-To: <20240604000417.16137-2-krisman@suse.de>
On 6/3/24 6:04 PM, Gabriel Krisman Bertazi wrote:
> Signed-off-by: Gabriel Krisman Bertazi <krisman@suse.de>
Finally got around to these, as the kernel support has landed...
> diff --git a/src/include/liburing.h b/src/include/liburing.h
> index 0a02364..818e27c 100644
> --- a/src/include/liburing.h
> +++ b/src/include/liburing.h
> @@ -669,6 +669,13 @@ IOURINGINLINE void io_uring_prep_connect(struct io_uring_sqe *sqe, int fd,
> io_uring_prep_rw(IORING_OP_CONNECT, sqe, fd, addr, 0, addrlen);
> }
>
> +IOURINGINLINE void io_uring_prep_bind(struct io_uring_sqe *sqe, int fd,
> + struct sockaddr *addr,
> + socklen_t addrlen)
> +{
> + io_uring_prep_rw(IORING_OP_BIND, sqe, fd, addr, 0, addrlen);
> +}
This needs an ffi and liburing-ffi.map entry as well. Ditto for the next
patch.
--
Jens Axboe
next prev parent reply other threads:[~2024-07-21 21:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 0:04 [RFC liburing 0/5] IORING_OP_BIND/LISTEN support Gabriel Krisman Bertazi
2024-06-04 0:04 ` [PATCH liburing 1/5] liburing: Add helper to prepare IORING_OP_BIND command Gabriel Krisman Bertazi
2024-07-21 21:18 ` Jens Axboe [this message]
2024-06-04 0:04 ` [PATCH liburing 2/5] liburing: Add helper to prepare IORING_OP_LISTEN command Gabriel Krisman Bertazi
2024-06-04 0:04 ` [PATCH liburing 3/5] tests: Add test for bind/listen commands Gabriel Krisman Bertazi
2024-07-21 21:21 ` Jens Axboe
2024-06-04 0:04 ` [PATCH liburing 4/5] man/io_uring_prep_bind.3: Document the IORING_OP_BIND operation Gabriel Krisman Bertazi
2024-06-04 0:04 ` [PATCH liburing 5/5] man/io_uring_prep_listen.3: Document IORING_OP_LISTEN operation Gabriel Krisman Bertazi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=403f0652-8f2d-400e-9f18-99b0b4085670@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=krisman@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox