From: Hannes Reinecke <hare@suse.de> To: "lsf-pc@lists.linux-foundation.org" <lsf-pc@lists.linux-foundation.org>, "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>, "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>, Linux NVMe Mailinglist <linux-nvme@lists.infradead.org> Subject: [LSF/MM/BPF TOPIC] block namespaces Date: Thu, 27 May 2021 10:01:11 +0200 [thread overview] Message-ID: <a189ec50-4c11-9ee9-0b9e-b492507adc1e@suse.de> (raw) Hi all, I guess it's time to tick off yet another item on my long-term to-do list: Block namespaces ---------------- Idea is similar to what network already does: allowing each user namespace to have a different 'view' on the existing block devices. EG if the admin creates a ramdisk in one namespace this device should not be visible to other namespaces. But for me the most important use-case would be qemu; currently the devices need to be set up in the host, even though the host has no business touching it as they really belong to the qemu instance. This is causing quite some irritation eg when this device has LVM or MD metadata and udev is trying to activate it on the host. Overall plan is to restrict views of '/dev', '/sys/dev/block' and '/sys/block' to only present the devices 'visible' for this namespace. Initially the drivers would keep their global enumeration, but plan is to make the drivers namespace-aware, too, such that each namespace could have its own driver-specific device enumeration. Goal of this topic is to get a consensus on whether block namespaces are a feature which would find interest, and also to discuss some design details here: - Only in certain cases can a namespace be assigned (eg by calling 'modprobe', starting iscsiadm, or calling nvme-cli); how do we handle devices for which no namespace can be identified? - Shall we allow for different device enumeration per namespace? - Into which level should we go with hiding sysfs structures? Is blanking out the higher-level interfaces in /dev and /sys/block enough? Cheers, Hannes -- Dr. Hannes Reinecke Kernel Storage Architect hare@suse.de +49 911 74053 688 SUSE Software Solutions Germany GmbH, 90409 Nürnberg GF: F. Imendörffer, HRB 36809 (AG Nürnberg)
WARNING: multiple messages have this Message-ID (diff)
From: Hannes Reinecke <hare@suse.de> To: "lsf-pc@lists.linux-foundation.org" <lsf-pc@lists.linux-foundation.org>, "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>, "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>, Linux NVMe Mailinglist <linux-nvme@lists.infradead.org> Subject: [LSF/MM/BPF TOPIC] block namespaces Date: Thu, 27 May 2021 10:01:11 +0200 [thread overview] Message-ID: <a189ec50-4c11-9ee9-0b9e-b492507adc1e@suse.de> (raw) Hi all, I guess it's time to tick off yet another item on my long-term to-do list: Block namespaces ---------------- Idea is similar to what network already does: allowing each user namespace to have a different 'view' on the existing block devices. EG if the admin creates a ramdisk in one namespace this device should not be visible to other namespaces. But for me the most important use-case would be qemu; currently the devices need to be set up in the host, even though the host has no business touching it as they really belong to the qemu instance. This is causing quite some irritation eg when this device has LVM or MD metadata and udev is trying to activate it on the host. Overall plan is to restrict views of '/dev', '/sys/dev/block' and '/sys/block' to only present the devices 'visible' for this namespace. Initially the drivers would keep their global enumeration, but plan is to make the drivers namespace-aware, too, such that each namespace could have its own driver-specific device enumeration. Goal of this topic is to get a consensus on whether block namespaces are a feature which would find interest, and also to discuss some design details here: - Only in certain cases can a namespace be assigned (eg by calling 'modprobe', starting iscsiadm, or calling nvme-cli); how do we handle devices for which no namespace can be identified? - Shall we allow for different device enumeration per namespace? - Into which level should we go with hiding sysfs structures? Is blanking out the higher-level interfaces in /dev and /sys/block enough? Cheers, Hannes -- Dr. Hannes Reinecke Kernel Storage Architect hare@suse.de +49 911 74053 688 SUSE Software Solutions Germany GmbH, 90409 Nürnberg GF: F. Imendörffer, HRB 36809 (AG Nürnberg) _______________________________________________ Linux-nvme mailing list Linux-nvme@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2021-05-27 8:01 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-27 8:01 Hannes Reinecke [this message] 2021-05-27 8:01 ` [LSF/MM/BPF TOPIC] block namespaces Hannes Reinecke 2021-06-09 18:36 ` James Bottomley 2021-06-09 18:36 ` James Bottomley 2021-06-10 5:49 ` Hannes Reinecke 2021-06-10 5:49 ` Hannes Reinecke 2021-06-10 14:29 ` James Bottomley 2021-06-10 14:29 ` James Bottomley 2021-06-10 15:05 ` Hannes Reinecke 2021-06-10 15:05 ` Hannes Reinecke
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=a189ec50-4c11-9ee9-0b9e-b492507adc1e@suse.de \ --to=hare@suse.de \ --cc=linux-block@vger.kernel.org \ --cc=linux-nvme@lists.infradead.org \ --cc=linux-scsi@vger.kernel.org \ --cc=lsf-pc@lists.linux-foundation.org \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.