Linux block layer
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Anuj Gupta <anuj20.g@samsung.com>
Cc: vincent.fu@samsung.com, anuj1072538@gmail.com, axboe@kernel.dk,
	hch@infradead.org, martin.petersen@oracle.com,
	shinichiro.kawasaki@wdc.com, linux-block@vger.kernel.org,
	joshi.k@samsung.com, gost.dev@samsung.com
Subject: Re: [blktests v1] block: add test for io_uring Protection Information (PI) interface using FS_IOC_GETLBMD_CAP
Date: Tue, 05 Aug 2025 22:51:47 -0400	[thread overview]
Message-ID: <yq17bzh9n8i.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20250805061655.65690-1-anuj20.g@samsung.com> (Anuj Gupta's message of "Tue, 5 Aug 2025 11:46:55 +0530")


Anuj,

> This test verifies end-to-end support for integrity metadata via the
> io-uring interface. It uses the FS_IOC_GETLBMD_CAP ioctl to query the
> logical block metadata capabilities of the device. These values are
> then passed to fio using the md_per_io_size option.

Looks OK to me.

Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>

-- 
Martin K. Petersen

  reply	other threads:[~2025-08-06  2:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20250805061730epcas5p4ae7a8eda6d1d11cc90317a80738eb2ea@epcas5p4.samsung.com>
2025-08-05  6:16 ` [blktests v1] block: add test for io_uring Protection Information (PI) interface using FS_IOC_GETLBMD_CAP Anuj Gupta
2025-08-06  2:51   ` Martin K. Petersen [this message]
2025-08-08 11:40   ` Shinichiro Kawasaki
2025-08-11 11:03     ` Anuj Gupta/Anuj Gupta
2025-08-13 11:24       ` Shinichiro Kawasaki
2025-09-19 10:12         ` Anuj Gupta/Anuj Gupta

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=yq17bzh9n8i.fsf@ca-mkp.ca.oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=anuj1072538@gmail.com \
    --cc=anuj20.g@samsung.com \
    --cc=axboe@kernel.dk \
    --cc=gost.dev@samsung.com \
    --cc=hch@infradead.org \
    --cc=joshi.k@samsung.com \
    --cc=linux-block@vger.kernel.org \
    --cc=shinichiro.kawasaki@wdc.com \
    --cc=vincent.fu@samsung.com \
    /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