From: Jens Axboe <axboe@kernel.dk>
To: Sitsofe Wheeler <sitsofe@gmail.com>, "Su, Friendy" <Friendy.Su@sony.com>
Cc: fio <fio@vger.kernel.org>,
"Kobayashi, Kento (Sony)" <Kento.A.Kobayashi@sony.com>
Subject: Re: [PATCH] engines: add engine for file stat
Date: Sun, 29 Dec 2019 16:20:41 -0700 [thread overview]
Message-ID: <027dde15-1c6a-47a5-f89b-0d808d4cd1f3@kernel.dk> (raw)
In-Reply-To: <CALjAwxjd9u+DLLOmf7reEtnkX=wL=vqK0dpCTq3cFHdVN0z7dg@mail.gmail.com>
On 12/29/19 2:23 PM, Sitsofe Wheeler wrote:
> On Thu, 19 Dec 2019 at 10:20, Su, Friendy <Friendy.Su@sony.com> wrote:
>>
>> Thanks for your comments.
>> I fixed and resent patch. Pls see my reply in text below.
>
> From a brief scan it looks OK to me but I'd say you are better off
> posting patches in-line because it make review easier (anyone else who
> wants to see it will have to look at the parent of this mail). If this
> is troublesome you can always try submitting a pull request (e.g. via
> https://github.com/axboe/fio/pulls )...
>
> Jens: If you can see the patch as an attachment (e.g. at the bottom of
> https://www.spinics.net/lists/fio/msg08203.html ), what do you think?
With my io_uring hat on, there's a few ways to do stat since io_uring
also supports it. Is the plan to enable a io_uring backend as well for
that engine? Or should stat perhaps be a data direction instead that all
io engines could then support, some of them in an async manner?
--
Jens Axboe
next prev parent reply other threads:[~2019-12-29 23:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 10:08 [PATCH] engines: add engine for file stat Friendy.Su
2019-12-17 10:28 ` Su, Friendy
2019-12-17 14:04 ` Sitsofe Wheeler
2019-12-19 10:19 ` Su, Friendy
2019-12-29 21:23 ` Sitsofe Wheeler
2019-12-29 23:20 ` Jens Axboe [this message]
2020-01-08 9:32 ` Su, Friendy
2020-01-21 10:09 ` Su, Friendy
2020-01-21 15:26 ` Jens Axboe
2020-01-22 3:05 ` Su, Friendy
2020-01-22 3:07 ` Su, Friendy
2020-01-22 15:32 ` Jens Axboe
2020-02-02 8:18 ` Su, Friendy
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=027dde15-1c6a-47a5-f89b-0d808d4cd1f3@kernel.dk \
--to=axboe@kernel.dk \
--cc=Friendy.Su@sony.com \
--cc=Kento.A.Kobayashi@sony.com \
--cc=fio@vger.kernel.org \
--cc=sitsofe@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