All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Meneghini <jmeneghi@redhat.com>
To: Hannes Reinecke <hare@suse.de>, Christoph Hellwig <hch@infradead.org>
Cc: "lsf-pc@lists.linux-foundation.org"
	<lsf-pc@lists.linux-foundation.org>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [LSF/MM/BPF TOPIC] dispersed namespaces revisited
Date: Wed, 23 Mar 2022 21:17:58 -0400	[thread overview]
Message-ID: <4e1aaadb-0044-6367-e4a6-e3f159fa007c@redhat.com> (raw)
In-Reply-To: <da128051-4d15-1566-2876-5167a0c1d033@suse.de>

I agree with Christoph that the current conception of dispersed namespaces fundamentally breaks the NVMe storage object model.

However, there have been several ideas proffered at FMDS to fix this and I think people are willing to make changes to TP-4034 
to redress this problem.

I think this is a topic that needs to be discussed at LSF/MM or ALPSS.

/John

On 3/23/22 13:16, Hannes Reinecke wrote:
> On 3/23/22 17:27, Christoph Hellwig wrote:
>> Hi Hannes,
>>
>> the answer is pretty simple:  dispersed namespaces are a bad idea and
>> will not be implemented in Linux, and this has been the stance since
>> this was first proposed.
>>
>> If these vendors want Linux support they can already trivially
>> implement virtual subsystems and are highly encouraged to do so.
>> (the concept of domains actually makes it even simpler than in
>> the beginning).
> 
> Guess what, that's what I have been proposing.
> And they have (somewhat) agreed.
> 
> I just wanted to use LSF to get everyone on board, and then be able to come with a proposal to NVMexpress which I know will be 
> acceptable from the Linux community.
> 
> I have a patchset ready implementing virtual subsystems based on the NS UUID (and thereby putting each namespace into a separate 
> subsystem).
> At this time it's just a PoC to demonstrate the concept; specification is not even proposed, and so it's hard to code against.
> 
> I can send a pointer to my kernel.org branch if you like.
> 
> Cheers,
> 
> Hannes



  parent reply	other threads:[~2022-03-24  1:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-23 16:20 [LSF/MM/BPF TOPIC] dispersed namespaces revisited Hannes Reinecke
2022-03-23 16:27 ` Christoph Hellwig
2022-03-23 17:16   ` Hannes Reinecke
2022-03-23 17:21     ` Christoph Hellwig
2022-03-24  1:17     ` John Meneghini [this message]
2022-03-24  5:42       ` Christoph Hellwig

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=4e1aaadb-0044-6367-e4a6-e3f159fa007c@redhat.com \
    --to=jmeneghi@redhat.com \
    --cc=hare@suse.de \
    --cc=hch@infradead.org \
    --cc=linux-nvme@lists.infradead.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: link
Be 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.