public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>,
	Kanchan Joshi <joshiiitr@gmail.com>
Cc: Kanchan Joshi <joshi.k@samsung.com>,
	viro@zeniv.linux.org.uk, bcrl@kvack.org, Damien.LeMoal@wdc.com,
	asml.silence@gmail.com, linux-fsdevel@vger.kernel.org,
	Matias Bj??rling <mb@lightnvm.io>,
	linux-kernel@vger.kernel.org, linux-aio@kvack.org,
	io-uring@vger.kernel.org, linux-block@vger.kernel.org,
	Selvakumar S <selvakuma.s1@samsung.com>,
	Nitesh Shetty <nj.shetty@samsung.com>,
	Javier Gonzalez <javier.gonz@samsung.com>
Subject: Re: [PATCH v3 4/4] io_uring: add support for zone-append
Date: Fri, 10 Jul 2020 08:09:33 -0600	[thread overview]
Message-ID: <9e870249-01db-c68d-ea65-28edc3c1f071@kernel.dk> (raw)
In-Reply-To: <20200710131054.GB7491@infradead.org>

On 7/10/20 7:10 AM, Christoph Hellwig wrote:
> On Fri, Jul 10, 2020 at 12:35:43AM +0530, Kanchan Joshi wrote:
>> Append required special treatment (conversion for sector to bytes) for io_uring.
>> And we were planning a user-space wrapper to abstract that.
>>
>> But good part (as it seems now) was: append result went along with cflags at
>> virtually no additional cost. And uring code changes became super clean/minimal
>> with further revisions.
>> While indirect-offset requires doing allocation/mgmt in application,
>> io-uring submission
>> and in completion path (which seems trickier), and those CQE flags
>> still get written
>> user-space and serve no purpose for append-write.
> 
> I have to say that storing the results in the CQE generally make
> so much more sense.  I wonder if we need a per-fd "large CGE" flag
> that adds two extra u64s to the CQE, and some ops just require this
> version.

I have been pondering the same thing, we could make certain ops consume
two CQEs if it makes sense. It's a bit ugly on the app side with two
different CQEs for a request, though. We can't just treat it as a large
CQE, as they might not be sequential if we happen to wrap. But maybe
it's not too bad.

-- 
Jens Axboe


  parent reply	other threads:[~2020-07-10 14:09 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20200705185204epcas5p3adeb4fc3473c5fc0472a7396783c5267@epcas5p3.samsung.com>
2020-07-05 18:47 ` [PATCH v3 0/4] zone-append support in io-uring and aio Kanchan Joshi
2020-07-05 18:47   ` [PATCH v3 1/4] fs: introduce FMODE_ZONE_APPEND and IOCB_ZONE_APPEND Kanchan Joshi
2020-07-05 18:47   ` [PATCH v3 2/4] block: add zone append handling for direct I/O path Kanchan Joshi
2020-07-05 18:47   ` [PATCH v3 3/4] block: enable zone-append for iov_iter of bvec type Kanchan Joshi
2020-07-05 18:47   ` [PATCH v3 4/4] io_uring: add support for zone-append Kanchan Joshi
2020-07-05 21:00     ` Jens Axboe
2020-07-05 21:09       ` Matthew Wilcox
2020-07-05 21:12         ` Jens Axboe
2020-07-06 14:10           ` Matthew Wilcox
2020-07-06 14:27             ` Jens Axboe
2020-07-06 14:32               ` Matthew Wilcox
2020-07-06 14:33                 ` Jens Axboe
2020-07-07 15:11                 ` Kanchan Joshi
2020-07-07 15:52                   ` Matthew Wilcox
2020-07-07 16:00                     ` Christoph Hellwig
2020-07-07 20:23                     ` Kanchan Joshi
2020-07-07 20:40                       ` Jens Axboe
2020-07-07 22:18                         ` Matthew Wilcox
2020-07-07 22:37                           ` Jens Axboe
2020-07-08 12:58                             ` Kanchan Joshi
2020-07-08 14:22                               ` Matthew Wilcox
2020-07-08 16:41                                 ` Kanchan Joshi
2020-07-08 14:54                               ` Jens Axboe
2020-07-08 14:58                                 ` Matthew Wilcox
2020-07-08 14:59                                   ` Jens Axboe
2020-07-08 15:02                                     ` Matthew Wilcox
2020-07-08 15:06                                       ` Jens Axboe
2020-07-08 16:08                                         ` Javier González
2020-07-08 16:33                                           ` Matthew Wilcox
2020-07-08 16:38                                             ` Jens Axboe
2020-07-08 17:13                                               ` Kanchan Joshi
2020-07-08 16:43                                             ` Javier González
2020-07-06 13:58       ` Kanchan Joshi
2020-07-09 10:15       ` Christoph Hellwig
2020-07-09 13:58         ` Jens Axboe
2020-07-09 14:00           ` Christoph Hellwig
2020-07-09 14:05             ` Jens Axboe
2020-07-09 18:36               ` Kanchan Joshi
2020-07-09 18:50                 ` Pavel Begunkov
2020-07-09 18:53                   ` Pavel Begunkov
2020-07-09 18:50                 ` Jens Axboe
2020-07-09 19:05                   ` Kanchan Joshi
2020-07-10 13:10                     ` Christoph Hellwig
2020-07-10 13:48                       ` Matthew Wilcox
2020-07-10 13:49                         ` Christoph Hellwig
2020-07-10 13:51                           ` Matthew Wilcox
2020-07-10 14:11                             ` Kanchan Joshi
2020-07-20 16:49                               ` Kanchan Joshi
2020-07-20 17:14                                 ` Matthew Wilcox
2020-07-20 20:17                                   ` Kanchan Joshi
2020-07-21  0:59                                     ` Damien Le Moal
2020-07-21  1:15                                       ` Matthew Wilcox
2020-07-21  1:29                                         ` Jens Axboe
2020-07-21  2:19                                         ` Damien Le Moal
2020-07-10 14:09                       ` Jens Axboe [this message]
2020-07-20 16:46                         ` Kanchan Joshi
2020-07-10 13:09                   ` Christoph Hellwig
2020-07-10 13:29                     ` Kanchan Joshi
2020-07-10 13:43                       ` Christoph Hellwig
2020-07-20 17:02                         ` Kanchan Joshi
2020-07-10 13:57                       ` 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=9e870249-01db-c68d-ea65-28edc3c1f071@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=Damien.LeMoal@wdc.com \
    --cc=asml.silence@gmail.com \
    --cc=bcrl@kvack.org \
    --cc=hch@infradead.org \
    --cc=io-uring@vger.kernel.org \
    --cc=javier.gonz@samsung.com \
    --cc=joshi.k@samsung.com \
    --cc=joshiiitr@gmail.com \
    --cc=linux-aio@kvack.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mb@lightnvm.io \
    --cc=nj.shetty@samsung.com \
    --cc=selvakuma.s1@samsung.com \
    --cc=viro@zeniv.linux.org.uk \
    /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