All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ankit Kumar <ankit1455@gmail.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Ankit Kumar <ankit.kumar@samsung.com>,
	fio@vger.kernel.org, krish.reddy@samsung.com,
	simon.lund@samsung.com, joshiiitr@gmail.com,
	anuj1072538@gmail.com
Subject: Re: [PATCH v2 0/3] fio: add xnvme engine
Date: Fri, 13 May 2022 16:36:16 +0530	[thread overview]
Message-ID: <CAKi7+weGb3AsfGKkHEiPNFDxQEKTDn68nb6cbfJNzM=+p+=3LA@mail.gmail.com> (raw)
In-Reply-To: <cf9dbc97-0847-6887-3d8f-320432bf5176@kernel.dk>

Thanks a lot for applying the xnvme engine changes. Yes we are adding
passthrough support in io_uring by having a separate ioengine_ops. The
changes will be ready shortly.

On Thu, May 12, 2022 at 5:58 PM Jens Axboe <axboe@kernel.dk> wrote:
>
> On 5/12/22 12:28 AM, Ankit Kumar wrote:
> > Yes we are using xnvme on various platforms, and it would be great if
> > it gets included as part of FIO.
> > For supporting io_uring engine with passthrough, yes we also have a
> > plan in place to clean up the code and send it for review.
>
> Sounds good. I've applied the xvnme engine, would appreciate if we can
> do the passthrough one shortly too. I'm wondering if that one is best
> done as a separate engine too - it could still be in engines/io_uring.c
> but have a separate ioengine_ops to keep the code nicely separated while
> still being able to use the same helpers in there.
>
> --
> Jens Axboe
>

  reply	other threads:[~2022-05-13 11:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20220511163552epcas5p4c2e1b204a47a543c24f84da89ef0c89a@epcas5p4.samsung.com>
2022-05-11 16:30 ` [PATCH v2 0/3] fio: add xnvme engine Ankit Kumar
     [not found]   ` <CGME20220511163555epcas5p11802150a9855558ab5823252f86dead3@epcas5p1.samsung.com>
2022-05-11 16:30     ` [PATCH 1/3] engines/xnvme: " Ankit Kumar
     [not found]   ` <CGME20220511163558epcas5p4c73dffb818b0dd543d813a480e07daa9@epcas5p4.samsung.com>
2022-05-11 16:30     ` [PATCH 2/3] docs: documentation for xnvme ioengine Ankit Kumar
     [not found]   ` <CGME20220511163600epcas5p23c957325fc8fb7cd935900b02c3cd73f@epcas5p2.samsung.com>
2022-05-11 16:30     ` [PATCH 3/3] examples: add example job file for xnvme engine usage Ankit Kumar
2022-05-11 19:19   ` [PATCH v2 0/3] fio: add xnvme engine Jens Axboe
2022-05-12  6:28     ` Ankit Kumar
2022-05-12 12:28       ` Jens Axboe
2022-05-13 11:06         ` Ankit Kumar [this message]
2022-05-12 12:26   ` Jens Axboe

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='CAKi7+weGb3AsfGKkHEiPNFDxQEKTDn68nb6cbfJNzM=+p+=3LA@mail.gmail.com' \
    --to=ankit1455@gmail.com \
    --cc=ankit.kumar@samsung.com \
    --cc=anuj1072538@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=joshiiitr@gmail.com \
    --cc=krish.reddy@samsung.com \
    --cc=simon.lund@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.