linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: John Meneghini <jmeneghi@redhat.com>,
	linux-block@vger.kernel.org, dm-devel@lists.linux.dev,
	linux-scsi@vger.kernel.org, Chris Leech <cleech@redhat.com>,
	Hannes Reinecke <hare@suse.de>, Christoph Hellwig <hch@lst.de>,
	snitzer@kernel.org, Ming Lei <minlei@redhat.com>,
	Benjamin Marzinski <bmarzins@redhat.com>,
	Jonathan Brassow <jbrassow@redhat.com>,
	Ewan Milne <emilne@redhat.com>,
	bmarson@redhat.com, Jeff Moyer <jmoyer@redhat.com>,
	"spetrovi@redhat.com" <spetrovi@redhat.com>,
	Rob Evers <revers@redhat.com>
Subject: Re: DMMP request-queue vs. BiO
Date: Fri, 15 Nov 2024 18:09:24 +0100	[thread overview]
Message-ID: <20241115170924.GB23437@lst.de> (raw)
In-Reply-To: <41cf98c3-a1de-a740-01ad-53c86f3bc8a5@redhat.com>

On Fri, Nov 15, 2024 at 03:05:21PM +0100, Mikulas Patocka wrote:
> Note, that if a database uses buffered block device, performance will be 
> suboptimal, because the buffering mechanism can't create large bios, it 
> only sends page-sized bios. But that is expected to not be used - the 
> database should either use a block device with direct I/O or a filesystem 
> with or without direct I/O.

And, as pointed out in the private mail that John forwarded to the list
without my permission if we really have a workload that cares md could
implement the plugging callback as done in md to operate on a batch
of bios.

Also not building large bios is not a fundamental property of block
device writes but because it uses the legacy buffered head helpers.
That means:

  a) the same is applicable to file systems using them as well
  b) can be fixed if someone cares enough, but apparently no one does


  reply	other threads:[~2024-11-15 17:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2d5fe016-2941-43a4-8b7c-850b8ee1d6ce@redhat.com>
     [not found] ` <20241104073547.GA20614@lst.de>
     [not found]   ` <d9733713-eb7b-4efa-ad6b-e6b41d1df93b@suse.de>
     [not found]     ` <20241105103307.GA1385@lst.de>
2024-11-07 18:35       ` DMMP request-queue vs. BiO John Meneghini
2024-11-15 14:05         ` Mikulas Patocka
2024-11-15 17:09           ` Christoph Hellwig [this message]
2024-11-15 20:28             ` John Meneghini
2024-11-18 13:05               ` Christoph Hellwig
2024-11-15 20:24           ` John Meneghini

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=20241115170924.GB23437@lst.de \
    --to=hch@lst.de \
    --cc=bmarson@redhat.com \
    --cc=bmarzins@redhat.com \
    --cc=cleech@redhat.com \
    --cc=dm-devel@lists.linux.dev \
    --cc=emilne@redhat.com \
    --cc=hare@suse.de \
    --cc=jbrassow@redhat.com \
    --cc=jmeneghi@redhat.com \
    --cc=jmoyer@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=minlei@redhat.com \
    --cc=mpatocka@redhat.com \
    --cc=revers@redhat.com \
    --cc=snitzer@kernel.org \
    --cc=spetrovi@redhat.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;
as well as URLs for NNTP newsgroup(s).