From: Chaitanya Kulkarni via iommu <iommu@lists.linux-foundation.org>
To: Martin Oliveira <Martin.Oliveira@eideticom.com>
Cc: Kelly Ursenbach <Kelly.Ursenbach@eideticom.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"Lee, Jason" <jasonlee@lanl.gov>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
Logan Gunthorpe <Logan.Gunthorpe@eideticom.com>
Subject: Re: Error when running fio against nvme-of rdma target (mlx5 driver)
Date: Wed, 9 Feb 2022 08:41:30 +0000 [thread overview]
Message-ID: <62fd851d-564e-e2f3-1a40-b594810d9f01@nvidia.com> (raw)
In-Reply-To: <MW3PR19MB42505C41C2BA3F425A5CB606E42D9@MW3PR19MB4250.namprd19.prod.outlook.com>
On 2/8/22 6:50 PM, Martin Oliveira wrote:
> Hello,
>
> We have been hitting an error when running IO over our nvme-of setup, using the mlx5 driver and we are wondering if anyone has seen anything similar/has any suggestions.
>
> Both initiator and target are AMD EPYC 7502 machines connected over RDMA using a Mellanox MT28908. Target has 12 NVMe SSDs which are exposed as a single NVMe fabrics device, one physical SSD per namespace.
>
Thanks for reporting this, if you can bisect the problem on your setup
it will help others to help you better.
-ck
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2022-02-09 8:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 2:50 Error when running fio against nvme-of rdma target (mlx5 driver) Martin Oliveira
2022-02-09 8:41 ` Chaitanya Kulkarni via iommu [this message]
2022-02-10 23:58 ` Martin Oliveira
2022-02-11 11:35 ` Robin Murphy
2022-05-17 8:26 ` Mark Ruijter
2022-05-17 11:16 ` Max Gurtovoy via iommu
2022-02-09 12:48 ` Robin Murphy
2024-01-31 9:18 ` Arthur Muller
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=62fd851d-564e-e2f3-1a40-b594810d9f01@nvidia.com \
--to=iommu@lists.linux-foundation.org \
--cc=Kelly.Ursenbach@eideticom.com \
--cc=Logan.Gunthorpe@eideticom.com \
--cc=Martin.Oliveira@eideticom.com \
--cc=chaitanyak@nvidia.com \
--cc=jasonlee@lanl.gov \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-rdma@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox