All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sachin Sant <sachinp@linux.ibm.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 0/3] io_uring READ(V), WRITE(v) operation tests
Date: Fri, 20 Mar 2026 18:17:39 +0530	[thread overview]
Message-ID: <20260320124742.75946-1-sachinp@linux.ibm.com> (raw)

This patch series adds a set of test case to validate
IOURING READ & WRITE (io_uring03), READV & WRITEV (io_uring04)
operations. The patch also adds a common header file to
avoid code duplication.

This patch series also refactors existing test io_uring01
to use the common structures and function defined in header.

These patches have been tested successfully on ppc64le
arch (fedora and SLES flavours)

Signed-off-by: Sachin Sant <sachinp@linux.ibm.com>
---
Changes from RFC patch series:
- Addressed review comments
- Refactored io_uring01 test to use common code
- Removed git tags
- Link to RFC: https://lore.kernel.org/ltp/20260318110328.52031-1-sachinp@linux.ibm.com/T/#t

Test run:

$ ./kirk -f iouring
....
Connecting to SUT: default

Suite: iouring
--------------
io_uring01: pass  (0.005s)
io_uring02: pass  (0.004s)
io_uring03: pass  (0.004s)
io_uring04: pass  (0.004s)

Execution time: 0.054s

Disconnecting from SUT: default

.....
------------------------
      TEST SUMMARY
------------------------
Suite:   iouring
Runtime: 0.017s
Runs:    4

Results:
    Passed:   23
    Failed:   0
    Broken:   0
    Skipped:  0
    Warnings: 0

Session stopped
$

---

Sachin Sant (3):
  io_uring: Test IORING READ and WRITE operations
  io_uring: Test READV and WRITEV operations
  io_uring: Refactor io_uring01 to use common code

 runtest/syscalls                              |   2 +
 testcases/kernel/syscalls/io_uring/.gitignore |   2 +
 .../kernel/syscalls/io_uring/io_uring01.c     | 111 +++-----
 .../kernel/syscalls/io_uring/io_uring03.c     | 130 +++++++++
 .../kernel/syscalls/io_uring/io_uring04.c     | 231 +++++++++++++++
 .../syscalls/io_uring/io_uring_common.h       | 265 ++++++++++++++++++
 6 files changed, 665 insertions(+), 76 deletions(-)
 create mode 100644 testcases/kernel/syscalls/io_uring/io_uring03.c
 create mode 100644 testcases/kernel/syscalls/io_uring/io_uring04.c
 create mode 100644 testcases/kernel/syscalls/io_uring/io_uring_common.h

-- 
2.39.1


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

             reply	other threads:[~2026-03-20 12:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-20 12:47 Sachin Sant [this message]
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
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=20260320124742.75946-1-sachinp@linux.ibm.com \
    --to=sachinp@linux.ibm.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.