public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: "hch@lst.de" <hch@lst.de>, Michael Kelley <mhklinux@outlook.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>
Subject: Re: Merging raw block device writes
Date: Mon, 27 Nov 2023 09:10:03 -0700	[thread overview]
Message-ID: <f2735bdc-1234-4477-a579-90bafa7ae4ea@kernel.dk> (raw)
In-Reply-To: <20231127065928.GA27811@lst.de>

On 11/26/23 11:59 PM, hch@lst.de wrote:
> On Sat, Nov 25, 2023 at 05:38:28PM +0000, Michael Kelley wrote:
>> Hyper-V guests and the Azure cloud have a particular interest here
>> because Hyper-V guests uses SCSI as the standard interface to virtual
>> disks.  Azure cloud disks can be throttled to a limited number of IOPS,
>> so the number of in-flights I/Os can be relatively high, and
>> merging can be beneficial to staying within the throttle
>> limits.  Of the flip side, this problem hasn't generated complaints
>> over the last 18 months that I'm aware of, though that may be more
>> because commercial distros haven't been running 5.16 or later kernels
>> until relatively recently.
> 
> I think the more important thing is that if you care about reducing
> the number of I/Os you probably should use an I/O scheduler.  Reducing
> the number of I/Os without an I/O scheduler isn't (and I'll argue
> shouldn't) be a concern for the non I/O scheduler.

Yep fully agree.

-- 
Jens Axboe


  reply	other threads:[~2023-11-27 16:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-25 17:38 Merging raw block device writes Michael Kelley
2023-11-27  6:59 ` hch
2023-11-27 16:10   ` Jens Axboe [this message]
2023-11-28 19:29     ` Michael Kelley
2023-11-28 21:59       ` 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=f2735bdc-1234-4477-a579-90bafa7ae4ea@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=mhklinux@outlook.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