public inbox for [email protected]
 help / color / mirror / Atom feed
From: Pavel Begunkov <[email protected]>
To: Ming Lei <[email protected]>, Bernd Schubert <[email protected]>
Cc: Jens Axboe <[email protected]>,
	Miklos Szeredi <[email protected]>,
	Christoph Hellwig <[email protected]>,
	Ziyang Zhang <[email protected]>,
	Xiaoguang Wang <[email protected]>,
	"[email protected]" 
	<[email protected]>,
	"[email protected]" <[email protected]>,
	"[email protected]" <[email protected]>
Subject: Re: [LSF/MM/BPF TOPIC] ublk & io_uring: ublk zero copy support
Date: Mon, 8 May 2023 03:16:10 +0100	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <ZFWviQb7eKn/[email protected]>

On 5/6/23 02:38, Ming Lei wrote:
> 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.

I'd love to go but regretfully can't make it

-- 
Pavel Begunkov

      reply	other threads:[~2023-05-08  2:22 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
2023-05-08  2:16     ` Pavel Begunkov [this message]

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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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