public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Kanchan Joshi <joshi.k@samsung.com>
To: axboe@kernel.dk, hch@lst.de
Cc: io-uring@vger.kernel.org, linux-nvme@lists.infradead.org,
	asml.silence@gmail.com, ming.lei@redhat.com, mcgrof@kernel.org,
	pankydev8@gmail.com, javier@javigon.com, joshiiitr@gmail.com,
	anuj20.g@samsung.com
Subject: [RFC 2/5] fs: add file_operations->async_cmd()
Date: Fri,  1 Apr 2022 16:33:07 +0530	[thread overview]
Message-ID: <20220401110310.611869-3-joshi.k@samsung.com> (raw)
In-Reply-To: <20220401110310.611869-1-joshi.k@samsung.com>

From: Jens Axboe <axboe@kernel.dk>

This is a file private handler, similar to ioctls but hopefully a lot
more sane and useful.

Signed-off-by: Jens Axboe <axboe@kernel.dk>
---
 include/linux/fs.h | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/include/linux/fs.h b/include/linux/fs.h
index e2d892b201b0..a32f83b70435 100644
--- a/include/linux/fs.h
+++ b/include/linux/fs.h
@@ -1977,6 +1977,7 @@ struct dir_context {
 #define REMAP_FILE_ADVISORY		(REMAP_FILE_CAN_SHORTEN)
 
 struct iov_iter;
+struct io_uring_cmd;
 
 struct file_operations {
 	struct module *owner;
@@ -2019,6 +2020,7 @@ struct file_operations {
 				   struct file *file_out, loff_t pos_out,
 				   loff_t len, unsigned int remap_flags);
 	int (*fadvise)(struct file *, loff_t, loff_t, int);
+	int (*async_cmd)(struct io_uring_cmd *ioucmd);
 } __randomize_layout;
 
 struct inode_operations {
-- 
2.25.1


  parent reply	other threads:[~2022-04-01 14:10 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20220401110829epcas5p39f3cf4d3f6eb8a5c59794787a2b72b15@epcas5p3.samsung.com>
2022-04-01 11:03 ` [RFC 0/5] big-cqe based uring-passthru Kanchan Joshi
2022-04-01 11:03   ` [RFC 1/5] io_uring: add support for 128-byte SQEs Kanchan Joshi
2022-04-01 11:03   ` Kanchan Joshi [this message]
2022-04-04  7:09     ` [RFC 2/5] fs: add file_operations->async_cmd() Christoph Hellwig
2022-04-01 11:03   ` [RFC 3/5] io_uring: add infra and support for IORING_OP_URING_CMD Kanchan Joshi
2022-04-04  7:16     ` Christoph Hellwig
2022-04-04  8:20       ` Pavel Begunkov
2022-04-05  5:58         ` Christoph Hellwig
2022-04-06  6:37           ` Kanchan Joshi
2022-04-04 15:14       ` Kanchan Joshi
2022-04-05  6:00         ` Christoph Hellwig
2022-04-05 16:27           ` Kanchan Joshi
2022-04-01 11:03   ` [RFC 4/5] io_uring: add support for big-cqe Kanchan Joshi
2022-04-04  7:07     ` Christoph Hellwig
2022-04-04 14:04       ` Kanchan Joshi
2022-04-01 11:03   ` [RFC 5/5] nvme: wire-up support for async-passthru on char-device Kanchan Joshi
2022-04-04  7:20     ` Christoph Hellwig
2022-04-04 14:25       ` Kanchan Joshi
2022-04-05  6:02         ` Christoph Hellwig
2022-04-05 15:40           ` Jens Axboe
2022-04-05 15:49           ` Kanchan Joshi
2022-04-06  5:20             ` Kanchan Joshi
2022-04-06  5:23               ` Christoph Hellwig
2022-04-23 17:53               ` Christoph Hellwig
2022-04-25 17:38                 ` Kanchan Joshi
2022-04-29 13:16                   ` Kanchan Joshi
2022-04-04  7:21   ` [RFC 0/5] big-cqe based uring-passthru Christoph Hellwig
2022-04-05 15:37     ` Kanchan Joshi

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=20220401110310.611869-3-joshi.k@samsung.com \
    --to=joshi.k@samsung.com \
    --cc=anuj20.g@samsung.com \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=io-uring@vger.kernel.org \
    --cc=javier@javigon.com \
    --cc=joshiiitr@gmail.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=mcgrof@kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=pankydev8@gmail.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