linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@lst.de>,
	Pavel Begunkov <asml.silence@gmail.com>,
	Anuj Gupta <anuj20.g@samsung.com>,
	kbusch@kernel.org, martin.petersen@oracle.com,
	anuj1072538@gmail.com, brauner@kernel.org, jack@suse.cz,
	viro@zeniv.linux.org.uk, io-uring@vger.kernel.org,
	linux-nvme@lists.infradead.org, linux-block@vger.kernel.org,
	gost.dev@samsung.com, linux-scsi@vger.kernel.org,
	vishak.g@samsung.com, linux-fsdevel@vger.kernel.org,
	Kanchan Joshi <joshi.k@samsung.com>
Subject: Re: [PATCH v9 06/11] io_uring: introduce attributes for read/write and PI support
Date: Fri, 15 Nov 2024 19:00:20 +0100	[thread overview]
Message-ID: <20241115180020.GA26128@lst.de> (raw)
In-Reply-To: <97b3061c-430d-4fc0-9b62-ab830010568e@kernel.dk>

On Fri, Nov 15, 2024 at 10:44:58AM -0700, Jens Axboe wrote:
> Let's please lay off the hyperbole here, uring_cmd would be a terrible
> way to do this. We're working through the flags requirements. Obviously
> this is now missing 6.13, but there's no reason why it's not on track to
> make 6.14 in a saner way.

I don't think it would actually be all that terrible.  Still not my
preferred option of course.


  reply	other threads:[~2024-11-15 18:00 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20241114105326epcas5p103b2c996293fa680092b97c747fdbd59@epcas5p1.samsung.com>
2024-11-14 10:45 ` [PATCH v9 00/11] Read/Write with meta/integrity Anuj Gupta
2024-11-14 10:45   ` [PATCH v9 01/11] block: define set of integrity flags to be inherited by cloned bip Anuj Gupta
2024-11-14 10:45   ` [PATCH v9 02/11] block: copy back bounce buffer to user-space correctly in case of split Anuj Gupta
2024-11-14 10:45   ` [PATCH v9 03/11] block: modify bio_integrity_map_user to accept iov_iter as argument Anuj Gupta
2024-11-14 10:45   ` [PATCH v9 04/11] fs, iov_iter: define meta io descriptor Anuj Gupta
2024-11-14 10:45   ` [PATCH v9 05/11] fs: introduce IOCB_HAS_METADATA for metadata Anuj Gupta
2024-11-14 10:45   ` [PATCH v9 06/11] io_uring: introduce attributes for read/write and PI support Anuj Gupta
2024-11-14 12:16     ` Christoph Hellwig
2024-11-14 13:09       ` Pavel Begunkov
2024-11-14 15:19         ` Christoph Hellwig
2024-11-15 16:40           ` Pavel Begunkov
2024-11-15 17:12             ` Christoph Hellwig
2024-11-15 17:44               ` Jens Axboe
2024-11-15 18:00                 ` Christoph Hellwig [this message]
2024-11-15 19:03               ` Pavel Begunkov
2024-11-18 12:49                 ` Christoph Hellwig
2024-11-15 18:04         ` Matthew Wilcox
2024-11-20 17:35           ` Darrick J. Wong
2024-11-21  6:54             ` Christoph Hellwig
2024-11-21 13:45             ` Pavel Begunkov
2024-11-15 13:29       ` Anuj gupta
2024-11-16  0:00     ` Pavel Begunkov
2024-11-16  0:32       ` Pavel Begunkov
2024-11-18 12:50         ` Christoph Hellwig
2024-11-18 16:59           ` Pavel Begunkov
2024-11-18 17:03             ` Christoph Hellwig
2024-11-18 17:45               ` Pavel Begunkov
2024-11-19 12:49                 ` Christoph Hellwig
2024-11-21 13:29                   ` Pavel Begunkov
2024-11-21  8:59             ` Anuj Gupta
2024-11-21 15:45               ` Pavel Begunkov
2024-11-16 23:09     ` kernel test robot
2024-11-14 10:45   ` [PATCH v9 07/11] io_uring: inline read/write attributes and PI Anuj Gupta
2024-11-14 10:45   ` [PATCH v9 08/11] block: introduce BIP_CHECK_GUARD/REFTAG/APPTAG bip_flags Anuj Gupta
2024-11-14 10:45   ` [PATCH v9 09/11] nvme: add support for passing on the application tag Anuj Gupta
2024-11-14 10:45   ` [PATCH v9 10/11] scsi: add support for user-meta interface Anuj Gupta
2024-11-14 10:45   ` [PATCH v9 11/11] block: add support to pass user meta buffer 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=20241115180020.GA26128@lst.de \
    --to=hch@lst.de \
    --cc=anuj1072538@gmail.com \
    --cc=anuj20.g@samsung.com \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=brauner@kernel.org \
    --cc=gost.dev@samsung.com \
    --cc=io-uring@vger.kernel.org \
    --cc=jack@suse.cz \
    --cc=joshi.k@samsung.com \
    --cc=kbusch@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=vishak.g@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;
as well as URLs for NNTP newsgroup(s).