public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Yang Xiuwei <yangxiuwei@kylinos.cn>
To: linux-scsi@vger.kernel.org, linux-block@vger.kernel.org,
	io-uring@vger.kernel.org
Cc: fujita.tomonori@lab.ntt.co.jp, axboe@kernel.dk,
	James.Bottomley@HansenPartnership.com,
	martin.petersen@oracle.com, Yang Xiuwei <yangxiuwei@kylinos.cn>
Subject: [RFC PATCH 1/3] bsg: add bsg_uring_cmd uapi structure
Date: Mon, 12 Jan 2026 16:46:04 +0800	[thread overview]
Message-ID: <20260112084606.570887-2-yangxiuwei@kylinos.cn> (raw)
In-Reply-To: <20260112084606.570887-1-yangxiuwei@kylinos.cn>

Add the bsg_uring_cmd structure to the BSG UAPI header to support
io_uring-based SCSI passthrough operations via IORING_OP_URING_CMD.

This structure is designed to work with 128-byte SQE (IO_URING_F_SQE128)
and provides a compact interface similar to sg_io_v4, but optimized
for io_uring's async I/O model. The structure is packed to fit within
the 80-byte cmd field of a 128-byte SQE, with 16 bytes reserved for
future extensions.

Key features:
- CDB address and length for SCSI command passthrough
- Protocol and subprotocol identifiers (BSG_PROTOCOL_SCSI)
- Data transfer parameters supporting both flat buffers and iovec arrays
- Sense data buffer information for error reporting
- Timeout and flags for command control

Signed-off-by: Yang Xiuwei <yangxiuwei@kylinos.cn>

diff --git a/include/uapi/linux/bsg.h b/include/uapi/linux/bsg.h
index cd6302def5ed..24b08fece509 100644
--- a/include/uapi/linux/bsg.h
+++ b/include/uapi/linux/bsg.h
@@ -63,5 +63,23 @@ struct sg_io_v4 {
 	__u32 padding;
 };
 
+struct bsg_uring_cmd {
+	__u64 cdb_addr;
+	__u8  cdb_len;
+	__u8  protocol;		/* [i] protocol type (BSG_PROTOCOL_*) */
+	__u8  subprotocol;	/* [i] subprotocol type (BSG_SUB_PROTOCOL_*) */
+	__u8  reserved1;
+	__u32 din_iovec_count;	/* [i] 0 -> flat din transfer else
+				 * din_xferp points to array of iovec
+				 */
+	__u32 din_xfer_len;	/* [i] bytes to be transferred from device */
+	__u64 din_xferp;	/* [i] data in buffer address or iovec array
+				 * address
+				 */
+	__u32 dout_iovec_count;	/* [i] 0 -> flat dout transfer else
+				 * dout_xferp points to array of iovec
+				 */
+	__u32 dout_xfer_len;	/* [i] bytes to be transferred to device */
+	__u64 dout_xferp;	/* [i] data out buffer address or iovec array address */
+	__u32 sense_len;
+	__u64 sense_addr;
+	__u32 timeout_ms;
+	__u32 flags;		/* [i] bit mask (BSG_FLAG_*) - reserved for future use */
+	__u8  reserved[16];	/* reserved for future extension */
+} __packed;
 
 #endif /* _UAPIBSG_H */
-- 
2.25.1


  reply	other threads:[~2026-01-12  8:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-12  8:46 [RFC PATCH 0/3] bsg: add io_uring command support for SCSI passthrough Yang Xiuwei
2026-01-12  8:46 ` Yang Xiuwei [this message]
2026-01-12 17:44   ` [RFC PATCH 1/3] bsg: add bsg_uring_cmd uapi structure Bart Van Assche
2026-01-13  1:26     ` Yang Xiuwei
2026-01-12  8:46 ` [RFC PATCH 2/3] bsg: add uring_cmd support to BSG generic layer Yang Xiuwei
2026-01-12  8:46 ` [RFC PATCH 3/3] bsg: implement SCSI BSG uring_cmd handler Yang Xiuwei

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=20260112084606.570887-2-yangxiuwei@kylinos.cn \
    --to=yangxiuwei@kylinos.cn \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=axboe@kernel.dk \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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