From: Caleb Sander Mateos <[email protected]>
To: Pavel Begunkov <[email protected]>
Cc: Jens Axboe <[email protected]>,
[email protected], [email protected]
Subject: Re: [PATCH] io_uring/rsrc: use rq_data_dir() to compute bvec dir
Date: Fri, 28 Feb 2025 17:42:10 -0800 [thread overview]
Message-ID: <CADUfDZpmnj8wCjaQcDTTT_rNhsegs0NFk6w393e+JsTg4MN+bQ@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
On Fri, Feb 28, 2025 at 5:23 PM Pavel Begunkov <[email protected]> wrote:
>
> On 2/28/25 22:30, Caleb Sander Mateos wrote:
> > The macro rq_data_dir() already computes a request's data direction.
> > Use it in place of the if-else to set imu->dir.
> >
> > Signed-off-by: Caleb Sander Mateos <[email protected]>
> > ---
> > io_uring/rsrc.c | 6 +-----
> > 1 file changed, 1 insertion(+), 5 deletions(-)
> >
> > diff --git a/io_uring/rsrc.c b/io_uring/rsrc.c
> > index 45bfb37bca1e..3107a03d56b8 100644
> > --- a/io_uring/rsrc.c
> > +++ b/io_uring/rsrc.c
> > @@ -957,15 +957,11 @@ int io_buffer_register_bvec(struct io_uring_cmd *cmd, struct request *rq,
> > imu->nr_bvecs = nr_bvecs;
> > refcount_set(&imu->refs, 1);
> > imu->release = release;
> > imu->priv = rq;
> > imu->is_kbuf = true;
> > -
> > - if (op_is_write(req_op(rq)))
> > - imu->dir = IO_IMU_SOURCE;
> > - else
> > - imu->dir = IO_IMU_DEST;
> > + imu->dir = 1 << rq_data_dir(rq);
>
> rq_data_dir returns READ/WRITE, which should be fine, but it'd
> be nicer to be more explicit unless it's already enforced
> somewhere else
>
> BUILD_BUG_ON(WRITE == ITER_SOURCE);
> ditto for READ
The definitions of ITER_SOURCE and ITER_DEST seem pretty clear that
they are aliases for WRITE/READ:
#define ITER_SOURCE 1 // == WRITE
#define ITER_DEST 0 // == READ
So I assume other code is already relying on this equivalence.
Best,
Caleb
next prev parent reply other threads:[~2025-03-01 1:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 22:30 [PATCH] io_uring/rsrc: use rq_data_dir() to compute bvec dir Caleb Sander Mateos
2025-03-01 1:24 ` Pavel Begunkov
2025-03-01 1:42 ` Caleb Sander Mateos [this message]
2025-03-01 2:01 ` Pavel Begunkov
2025-03-01 2:23 ` Jens Axboe
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=CADUfDZpmnj8wCjaQcDTTT_rNhsegs0NFk6w393e+JsTg4MN+bQ@mail.gmail.com \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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