From: Demi Marie Obenour <demi@invisiblethingslab.com>
To: Gionatan Danti <g.danti@assyoma.it>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM performance vs direct dm-thin
Date: Sun, 30 Jan 2022 16:17:17 -0500 [thread overview]
Message-ID: <YfcAucYQ+GIMpW6t@itl-email> (raw)
In-Reply-To: <d6edb2859c355a842a87b897106832a0@assyoma.it>
[-- Attachment #1.1: Type: text/plain, Size: 864 bytes --]
On Sun, Jan 30, 2022 at 09:27:56PM +0100, Gionatan Danti wrote:
> Il 2022-01-30 18:43 Zdenek Kabelac ha scritto:
> > Chain filesystem->block_layer->filesystem->block_layer is something
> > you most likely do not want to use for any well performing solution...
> > But it's ok for testing...
>
> I second that.
>
> Demi Marie - just a question: are you sure do you really needs a block
> device? I don't know QubeOS, but both KVM and Xen can use files as virtual
> disks. This would enable you to ignore loopback mounts.
On Xen, the paravirtualised block backend driver (blkback) requires a
block device, so file-based virtual disks are implemented with a loop
device managed by the toolstack. Suggestions for improving this
less-than-satisfactory situation are welcome.
--
Sincerely,
Demi Marie Obenour (she/her/hers)
Invisible Things Lab
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next prev parent reply other threads:[~2022-01-30 21:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 20:34 [linux-lvm] LVM performance vs direct dm-thin Demi Marie Obenour
2022-01-29 21:32 ` Zdenek Kabelac
2022-01-30 0:32 ` Demi Marie Obenour
2022-01-30 10:52 ` Zdenek Kabelac
2022-01-30 16:45 ` Demi Marie Obenour
2022-01-30 17:43 ` Zdenek Kabelac
2022-01-30 20:27 ` Gionatan Danti
2022-01-30 21:17 ` Demi Marie Obenour [this message]
2022-01-31 7:52 ` Gionatan Danti
2022-02-02 2:09 ` Demi Marie Obenour
2022-02-02 10:04 ` Zdenek Kabelac
2022-02-03 0:23 ` Demi Marie Obenour
2022-02-03 12:04 ` Zdenek Kabelac
2022-02-03 12:04 ` Zdenek Kabelac
2022-01-30 21:39 ` Stuart D. Gathman
2022-01-30 22:14 ` Demi Marie Obenour
2022-01-31 21:29 ` Marian Csontos
2022-02-03 4:48 ` Demi Marie Obenour
2022-02-03 12:28 ` Zdenek Kabelac
2022-02-04 0:01 ` Demi Marie Obenour
2022-02-04 10:16 ` Zdenek Kabelac
2022-01-31 7:47 ` Gionatan Danti
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=YfcAucYQ+GIMpW6t@itl-email \
--to=demi@invisiblethingslab.com \
--cc=g.danti@assyoma.it \
--cc=linux-lvm@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).