From: Sachin Sant <sachinp@linux.ibm.com>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 2/3] io_uring: Test READV and WRITEV operations
Date: Tue, 24 Mar 2026 10:45:56 +0530 [thread overview]
Message-ID: <3a221c0c-abe8-4483-bcbf-1fe0ebb5df8f@linux.ibm.com> (raw)
In-Reply-To: <acFo4gfmugdfiOwI@yuki.lan>
On 23/03/26 9:52 pm, Cyril Hrubis wrote:
> Hi!
>> +#define TEST_FILE "io_uring_test_file"
>> +#define QUEUE_DEPTH 2
>> +#define NUM_VECS 4
>> +#define VEC_SIZE 1024
>> +
>> +static char write_bufs[NUM_VECS][VEC_SIZE];
>> +static char read_bufs[NUM_VECS][VEC_SIZE];
>> +static struct iovec write_iovs[NUM_VECS];
>> +static struct iovec read_iovs[NUM_VECS];
> The guarded buffers can allocate iovec for you as well. Have a look at
> readv01.c test how to do that in the tst_test structure.
Thanks Cyril for the review comments. I have addressed them in v2.
--
Thanks
- Sachin
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-03-24 5:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 12:47 [LTP] [PATCH 0/3] io_uring READ(V), WRITE(v) operation tests Sachin Sant
2026-03-20 12:47 ` [LTP] [PATCH 1/3] io_uring: Test IORING READ and WRITE operations Sachin Sant
2026-03-23 12:46 ` Cyril Hrubis
2026-03-23 15:46 ` Sachin Sant
2026-03-20 12:47 ` [LTP] [PATCH 2/3] io_uring: Test READV and WRITEV operations Sachin Sant
2026-03-23 16:22 ` Cyril Hrubis
2026-03-24 5:15 ` Sachin Sant [this message]
2026-03-20 12:47 ` [LTP] [PATCH 3/3] io_uring: Refactor io_uring01 to use common code Sachin Sant
2026-03-23 16:32 ` Cyril Hrubis
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=3a221c0c-abe8-4483-bcbf-1fe0ebb5df8f@linux.ibm.com \
--to=sachinp@linux.ibm.com \
--cc=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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