From: Tom Talpey <tom@talpey.com>
To: Steve French <smfrench@gmail.com>, David Howells <dhowells@redhat.com>
Cc: Namjae Jeon <linkinjeon@kernel.org>,
Long Li <longli@microsoft.com>, Hyunchul Lee <hyc.lee@gmail.com>,
CIFS <linux-cifs@vger.kernel.org>
Subject: Re: RDMA (smbdirect) testing
Date: Tue, 24 May 2022 14:12:32 -0400 [thread overview]
Message-ID: <b02843ce-48ea-29b1-c032-575e08be622b@talpey.com> (raw)
In-Reply-To: <CAH2r5mt83Hxj_bT=y0G5XieEka6bATvt7Z0jKhcFDEuA-2u+hQ@mail.gmail.com>
On 5/24/2022 1:49 PM, Steve French wrote:
> Or alternatively - the "query network interfaces" ioctl - wonder if
> additional flags that could be added (beyond what is defined in
> MS-SMB2 2.2.32.5
Huh? I see no reason to expose this over the wire, it's entirely a local
device API question. Zero impact on the far side of the connection.
> On Tue, May 24, 2022 at 4:16 AM David Howells <dhowells@redhat.com> wrote:
>>
>> Is there some way for cifs to ask the RDMA layer what it supports?
Yes, and in fact the client and server already fetch it. It's a
standard verbs device attibute.
client fs/cifs/smbdirect.c:
> if (info->id->device->attrs.max_send_sge < SMBDIRECT_MAX_SGE) {
> log_rdma_event(ERR,
> "warning: device max_send_sge = %d too small\n",
> info->id->device->attrs.max_send_sge);
> log_rdma_event(ERR, "Queue Pair creation may fail\n");
> }
> if (info->id->device->attrs.max_recv_sge < SMBDIRECT_MAX_SGE) {
> log_rdma_event(ERR,
> "warning: device max_recv_sge = %d too small\n",
> info->id->device->attrs.max_recv_sge);
> log_rdma_event(ERR, "Queue Pair creation may fail\n");
> }
server fs/ksmbd/transport_rdma.c:
>
> if (device->attrs.max_send_sge < SMB_DIRECT_MAX_SEND_SGES) {
> pr_err("warning: device max_send_sge = %d too small\n",
> device->attrs.max_send_sge);
> return -EINVAL;
> }
> if (device->attrs.max_recv_sge < SMB_DIRECT_MAX_RECV_SGES) {
> pr_err("warning: device max_recv_sge = %d too small\n",
> device->attrs.max_recv_sge);
> return -EINVAL;
> }
Tom.
next prev parent reply other threads:[~2022-05-24 18:13 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 [this message]
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
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=b02843ce-48ea-29b1-c032-575e08be622b@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