Linux block layer
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Bernd Schubert <bschubert@ddn.com>
Cc: Jens Axboe <axboe@kernel.dk>,
	Pavel Begunkov <asml.silence@gmail.com>,
	Miklos Szeredi <mszeredi@redhat.com>,
	Christoph Hellwig <hch@lst.de>,
	Ziyang Zhang <ZiyangZhang@linux.alibaba.com>,
	Xiaoguang Wang <xiaoguang.wang@linux.alibaba.com>,
	"lsf-pc@lists.linux-foundation.org" 
	<lsf-pc@lists.linux-foundation.org>,
	"io-uring@vger.kernel.org" <io-uring@vger.kernel.org>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [LSF/MM/BPF TOPIC] ublk & io_uring: ublk zero copy support
Date: Sat, 6 May 2023 09:38:17 +0800	[thread overview]
Message-ID: <ZFWviQb7eKn/eBi9@ovpn-8-16.pek2.redhat.com> (raw)
In-Reply-To: <41cfb9c2-9774-e9e1-d8e7-4999a710f2e7@ddn.com>

On Fri, May 05, 2023 at 09:57:47PM +0000, Bernd Schubert wrote:
> Hi Ming,
> 
> On 4/29/23 04:18, Ming Lei wrote:
> > Hello,
> > 
> > ublk zero copy is observed to improve big chunk(64KB+) sequential IO performance a
> > lot, such as, IOPS of ublk-loop over tmpfs is increased by 1~2X[1], Jens also observed
> > that IOPS of ublk-qcow2 can be increased by ~1X[2]. Meantime it saves memory bandwidth.
> > 
> > So this is one important performance improvement.
> > 
> > So far there are three proposal:
> 
> looks like there is no dedicated session. Could we still have a 
> discussion in a free slot, if possible?

Sure, and we can invite Pavel to the talk too if he is in this lsfmm.


thanks,
Ming


  reply	other threads:[~2023-05-06  1:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-29  2:18 [LSF/MM/BPF TOPIC] ublk & io_uring: ublk zero copy support Ming Lei
2023-05-05 21:57 ` Bernd Schubert
2023-05-06  1:38   ` Ming Lei [this message]
2023-05-08  2:16     ` Pavel Begunkov

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=ZFWviQb7eKn/eBi9@ovpn-8-16.pek2.redhat.com \
    --to=ming.lei@redhat.com \
    --cc=ZiyangZhang@linux.alibaba.com \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=bschubert@ddn.com \
    --cc=hch@lst.de \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=mszeredi@redhat.com \
    --cc=xiaoguang.wang@linux.alibaba.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