All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Hans Holmberg <Hans.Holmberg@wdc.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"Matias Bjørling" <Matias.Bjorling@wdc.com>,
	"Damien Le Moal" <Damien.LeMoal@wdc.com>,
	"Dennis Maisenbacher" <dennis.maisenbacher@wdc.com>,
	"Ajay Joshi" <Ajay.Joshi@wdc.com>,
	"Jørgen Hansen" <Jorgen.Hansen@wdc.com>,
	"andreas@metaspace.dk" <andreas@metaspace.dk>,
	"javier@javigon.com" <javier@javigon.com>,
	"slava@dubeyko.com" <slava@dubeyko.com>,
	"kbusch@kernel.org" <kbusch@kernel.org>,
	"hans@owltronix.com" <hans@owltronix.com>,
	"mcgrof@kernel.org" <mcgrof@kernel.org>,
	"guokuankuan@bytedance.com" <guokuankuan@bytedance.com>,
	"viacheslav.dubeyko@bytedance.com"
	<viacheslav.dubeyko@bytedance.com>, "hch@lst.de" <hch@lst.de>
Subject: Re: [LSF/MM/BPF BoF]: A host FTL for zoned block devices using UBLK
Date: Mon, 6 Feb 2023 20:54:36 +0800	[thread overview]
Message-ID: <Y+D4jImmZ2r3Wazg@T590> (raw)
In-Reply-To: <Y+D3Sy8v3taelXvF@T590>

On Mon, Feb 06, 2023 at 08:49:15PM +0800, Ming Lei wrote:
> > ublk adds a bit of latency overhead, but I think this is acceptable at least
> > until we have a great, proven solution, which could be turned into
> > an in-kernel FTL.
> 
> We will keep improving ublk io path, and I am working on ublk
> copy. Once it is done, big chunk IO latency could be reduced a lot.

s/copy/zero copy


Thanks,
Ming


  reply	other threads:[~2023-02-06 12:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-06 10:00 [LSF/MM/BPF BoF]: A host FTL for zoned block devices using UBLK Hans Holmberg
2023-02-06 12:49 ` Ming Lei
2023-02-06 12:54   ` Ming Lei [this message]
2023-02-06 14:34   ` Matias Bjørling
2023-02-06 15:32     ` Ming Lei
2023-02-06 18:31     ` Bart Van Assche
2023-02-07  9:40       ` Matias Bjørling
2023-02-07  9:32     ` Hans Holmberg
2023-02-07 10:31   ` Nitesh Shetty
2023-02-07 12:49     ` Ming Lei
2023-02-06 18:58 ` Bart Van Assche
2023-02-07 12:11   ` Hans Holmberg

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=Y+D4jImmZ2r3Wazg@T590 \
    --to=ming.lei@redhat.com \
    --cc=Ajay.Joshi@wdc.com \
    --cc=Damien.LeMoal@wdc.com \
    --cc=Hans.Holmberg@wdc.com \
    --cc=Jorgen.Hansen@wdc.com \
    --cc=Matias.Bjorling@wdc.com \
    --cc=andreas@metaspace.dk \
    --cc=dennis.maisenbacher@wdc.com \
    --cc=guokuankuan@bytedance.com \
    --cc=hans@owltronix.com \
    --cc=hch@lst.de \
    --cc=javier@javigon.com \
    --cc=kbusch@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=slava@dubeyko.com \
    --cc=viacheslav.dubeyko@bytedance.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.