On 21-01-15 18:47:20, Klaus Jensen wrote:
> On Jan 15 09:35, Keith Busch wrote:
> > On Fri, Jan 15, 2021 at 02:57:45PM +0100, Klaus Jensen wrote:
> > >
> > > As you already mentioned, the problem I see with this approach is that
> > > we have separate namespaces attached to separate controllers.
On Fri, Jan 15, 2021 at 06:47:20PM +0100, Klaus Jensen wrote:
> Cool!
I thought so too :)
> Question: NSIDs must be the same on each controller for shared
> namespaces, but can private namespaces "share" nsid across controllers
> in the subsystem? I don't think the spec is clear on that point.
On Jan 15 09:35, Keith Busch wrote:
> On Fri, Jan 15, 2021 at 02:57:45PM +0100, Klaus Jensen wrote:
> >
> > As you already mentioned, the problem I see with this approach is that
> > we have separate namespaces attached to separate controllers. So we are
> > faking it to the max and if I/O starts
On Fri, Jan 15, 2021 at 02:57:45PM +0100, Klaus Jensen wrote:
>
> As you already mentioned, the problem I see with this approach is that
> we have separate namespaces attached to separate controllers. So we are
> faking it to the max and if I/O starts going through the other
> controller we end
On Jan 15 21:05, Minwoo Im wrote:
> Hello,
>
> This series added support for multi-path I/O with multi-controllers and
> namespace sharing. By supporting these features, we can test Linux
> kernel mpath(multi-path) code with this NVMe device.
>
> Patches from the first to third added
Hello,
This series added support for multi-path I/O with multi-controllers and
namespace sharing. By supporting these features, we can test Linux
kernel mpath(multi-path) code with this NVMe device.
Patches from the first to third added multi-controller support in a NVM
subsystem by adding a
