|
From: | Eric Blake |
Subject: | Re: virtiofsd: Where should it live? |
Date: | Wed, 4 Dec 2019 08:34:44 -0600 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2 |
On 12/4/19 1:43 AM, Markus Armbruster wrote:
+- qemu-img | +- qemu-img.cPerhaps this one can all go into existing block/, similar to how pr-manager-helper.c is in scsi/, and virtfs-proxy-helper.c is in fsdev/. Up to the block maintainers, of course.+- qemu-nbd | +- qemu-nbd.cblock/ or nbd/?
I'd lean towards nbd/, but am open to opinions from other block maintainers. Kevin's plan to add a generic block utility that includes the functionality of qemu-nbd may also matter (where block/ starts to sound better).
+- qemu-io | +- qemu-io.c | +- qemu-io-cmds.cblock/?
qemu-img and qemu-io in block/ sound reasonable to me. -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3226 Virtualization: qemu.org | libvirt.org
[Prev in Thread] | Current Thread | [Next in Thread] |