From: Tom Talpey <tom@talpey.com>
To: David Howells <dhowells@redhat.com>, Namjae Jeon <linkinjeon@kernel.org>
Cc: Long Li <longli@microsoft.com>, Hyunchul Lee <hyc.lee@gmail.com>,
Steve French <smfrench@gmail.com>,
CIFS <linux-cifs@vger.kernel.org>
Subject: Re: RDMA (smbdirect) testing
Date: Mon, 23 May 2022 09:37:31 -0400 [thread overview]
Message-ID: <9cd02802-c593-0246-43f4-43047eb06fda@talpey.com> (raw)
In-Reply-To: <747882.1653311226@warthog.procyon.org.uk>
On 5/23/2022 9:07 AM, David Howells wrote:
> Namjae Jeon <linkinjeon@kernel.org> wrote:
>
>> No. I was able to reproduce the same problem that David reported. I
>> and Hyunchul will take a look. I also confirmed that RDMA work well
>> without any problems with soft-ROCE. Until this problem is fixed, I'd
>> like to say David to use soft-ROCE.
>
> I managed to set up soft-RoCE and get cifs working over that.
>
> One thing I'm not sure about: on my server, I see the roce device with
> ibv_devices, but on my test client, I don't. I'm wondering if there's
> something I need to configure to get that.
Probably not, but I'd recommend to avoid wading into that if your
testing is going ok. Send a report to linux-rdma and let them know,
if so?
We are told that RedHat is removing SoftRoCE from RHEL9, this too might
affect your future testing plans...
Tom.
> I've attached the config for reference. Note that I build a monolithic kernel
> so that I can PXE boot it directly out of the build dir rather than building
> and installing a fresh rpm each time.
>
> David
next prev parent reply other threads:[~2022-05-23 13:37 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 20:41 RDMA (smbdirect) testing Steve French
2022-05-19 23:06 ` Namjae Jeon
2022-05-20 6:01 ` Hyunchul Lee
2022-05-20 18:03 ` Tom Talpey
2022-05-20 18:12 ` David Howells
2022-05-21 11:54 ` Tom Talpey
2022-05-22 23:06 ` Namjae Jeon
2022-05-23 13:45 ` Tom Talpey
2022-05-23 15:05 ` Namjae Jeon
2022-05-23 16:05 ` Tom Talpey
2022-05-23 19:17 ` Long Li
2022-05-24 1:01 ` Namjae Jeon
2022-05-24 21:08 ` Long Li
2022-06-02 23:32 ` Namjae Jeon
2022-06-03 0:07 ` Long Li
2022-06-07 17:26 ` Tom Talpey
2022-06-07 22:25 ` Namjae Jeon
2022-05-24 0:59 ` Namjae Jeon
2022-05-24 9:16 ` David Howells
2022-05-24 17:49 ` Steve French
2022-05-24 18:12 ` Tom Talpey
2022-05-25 9:29 ` David Howells
2022-05-25 9:41 ` David Howells
2022-05-25 10:00 ` Stefan Metzmacher
2022-05-25 10:20 ` David Howells
2022-05-26 14:56 ` Stefan Metzmacher
2022-05-26 15:52 ` Tom Talpey
2022-05-27 8:27 ` Stefan Metzmacher
2022-05-27 11:46 ` David Howells
2022-05-27 13:45 ` Stefan Metzmacher
2022-05-27 22:22 ` David Howells
2022-08-02 15:10 ` David Howells
2022-08-03 0:55 ` Namjae Jeon
2022-08-03 2:36 ` Namjae Jeon
2022-08-03 6:16 ` David Howells
[not found] ` <747882.1653311226@warthog.procyon.org.uk>
2022-05-23 13:37 ` Tom Talpey [this message]
2022-05-23 14:03 ` Stefan Metzmacher
2022-05-25 9:35 ` David Howells
2022-05-20 6:20 ` David Howells
2022-05-20 8:37 ` Namjae Jeon
2022-05-24 20:12 ` David Howells
2022-05-27 10:33 ` UAF in smbd_reconnect() when using softIWarp David Howells
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=9cd02802-c593-0246-43f4-43047eb06fda@talpey.com \
--to=tom@talpey.com \
--cc=dhowells@redhat.com \
--cc=hyc.lee@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=smfrench@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox