Linux block layer
 help / color / mirror / Atom feed
* Is LO_FLAGS_DIRECT_IO by default a good idea?
@ 2021-10-18 14:19 Lennart Poettering
  2021-10-18 15:05 ` Christoph Hellwig
  0 siblings, 1 reply; 6+ messages in thread
From: Lennart Poettering @ 2021-10-18 14:19 UTC (permalink / raw)
  To: Christoph Hellwig, Jens Axboe, Ming Lei, Martijn Coenen
  Cc: linux-block, Luca Boccassi, Karel Zak

eMing, Christoph, Jens!

Ming, 5 years ago or so you added support for dio/aio for the
loopback block device, i.e. LO_FLAGS_DIRECT_IO. As I understood it's
supposed to improve performance of loopback block devices
substantially. I noticed that there's various software that enables it
by default (Android, Docker), but a lot of other candidates currently
do not (util-linux, Ubuntu Snaps, various systemd tools). We recently
got a request to enable it by default in systemd, but information is
scarce on the precise effect of enabling this, and whether there are
any drawbacks.

So my question really is just: is this a flag we should all just
enable by default? Is there any reason not to enable it? Should
util-linux' losetup defaults be changed regarding this?

A brief answer like "yes, please, enable by default" would already
make me happy.

Thank you,

Lennart

--
Lennart Poettering, Berlin

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2021-10-25 10:38 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2021-10-18 14:19 Is LO_FLAGS_DIRECT_IO by default a good idea? Lennart Poettering
2021-10-18 15:05 ` Christoph Hellwig
2021-10-19  7:28   ` Lennart Poettering
2021-10-19  7:44   ` Ming Lei
2021-10-19 12:24     ` Jens Axboe
2021-10-25 10:37       ` Karel Zak

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox