From: loberman@redhat.com (Laurence Oberman)
Subject: Regression: Connect-X5 doesn't connect with NVME-of
Date: Mon, 05 Feb 2018 10:44:32 -0500 [thread overview]
Message-ID: <1517845472.11655.3.camel@redhat.com> (raw)
In-Reply-To: <7941ee6c-bf13-093c-e5c2-9ed93889405d@grimberg.me>
On Mon, 2018-02-05@16:18 +0200, Sagi Grimberg wrote:
> > Hi Sagi/Logan,
> >
> > I've repro it with v4.14.1 (not happens on each connect).
> > Sagi's proposal below fix the issue of the "Failed to write to?
> > /dev/nvme-fabrics: Invalid cross-device link".
> >
> > Sagi can you push (with my Tested-by: Max Gurtovoy <maxg at mellanox.c
> > om>?
> > and Reviewed-by: Max Gurtovoy <maxg at mellanox.com>) it or I will ?
>
> Thanks, I'll send it.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma"
> in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at??http://vger.kernel.org/majordomo-info.html
This missed me because all my NVME is still using CX3 (mlx4)
I will move the NVME devices into the setup with mlx5 so next time I
will catch this sort of issue with the testing.
Currently the mlx5 is only testing ISER and SRP.
Thanks
Laurence
WARNING: multiple messages have this Message-ID (diff)
From: Laurence Oberman <loberman-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Sagi Grimberg <sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>,
Max Gurtovoy <maxg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
Saeed Mahameed <saeedm-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
Logan Gunthorpe <logang-OTvnGxWRz7hWk0Htik3J/w@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: Stephen Bates <sbates-pv7U853sEMVWk0Htik3J/w@public.gmane.org>,
linux-nvme
<linux-nvme-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
Subject: Re: Regression: Connect-X5 doesn't connect with NVME-of
Date: Mon, 05 Feb 2018 10:44:32 -0500 [thread overview]
Message-ID: <1517845472.11655.3.camel@redhat.com> (raw)
In-Reply-To: <7941ee6c-bf13-093c-e5c2-9ed93889405d-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
On Mon, 2018-02-05 at 16:18 +0200, Sagi Grimberg wrote:
> > Hi Sagi/Logan,
> >
> > I've repro it with v4.14.1 (not happens on each connect).
> > Sagi's proposal below fix the issue of the "Failed to write to
> > /dev/nvme-fabrics: Invalid cross-device link".
> >
> > Sagi can you push (with my Tested-by: Max Gurtovoy <maxg@mellanox.c
> > om>
> > and Reviewed-by: Max Gurtovoy <maxg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>) it or I will ?
>
> Thanks, I'll send it.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma"
> in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
This missed me because all my NVME is still using CX3 (mlx4)
I will move the NVME devices into the setup with mlx5 so next time I
will catch this sort of issue with the testing.
Currently the mlx5 is only testing ISER and SRP.
Thanks
Laurence
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-02-05 15:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 17:56 Regression: Connect-X5 doesn't connect with NVME-of Logan Gunthorpe
[not found] ` <66a5332c-01ee-7a39-8224-189fa52a7298-OTvnGxWRz7hWk0Htik3J/w@public.gmane.org>
2018-02-03 4:53 ` Saeed Mahameed
[not found] ` <e6cdfbe7-762c-c70c-be5f-397bdb08ee80-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2018-02-03 22:46 ` Max Gurtovoy
2018-02-04 9:57 ` Sagi Grimberg
2018-02-04 9:57 ` Sagi Grimberg
2018-02-05 11:23 ` Max Gurtovoy
2018-02-05 11:23 ` Max Gurtovoy
2018-02-05 14:18 ` Sagi Grimberg
2018-02-05 14:18 ` Sagi Grimberg
2018-02-05 15:44 ` Laurence Oberman [this message]
2018-02-05 15:44 ` Laurence Oberman
2018-02-05 15:59 ` Max Gurtovoy
2018-02-05 15:59 ` Max Gurtovoy
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=1517845472.11655.3.camel@redhat.com \
--to=loberman@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 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.