From: David Howells <dhowells@redhat.com>
To: Namjae Jeon <linkinjeon@kernel.org>
Cc: dhowells@redhat.com, Tom Talpey <tom@talpey.com>,
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: Wed, 25 May 2022 10:29:59 +0100 [thread overview]
Message-ID: <1922487.1653470999@warthog.procyon.org.uk> (raw)
In-Reply-To: <CAKYAXd-PezRG4i-7DCiNAMQ0H9DsX-aDxD1rJavEzCmMa179xg@mail.gmail.com>
Namjae Jeon <linkinjeon@kernel.org> wrote:
> diff --git a/fs/cifs/smbdirect.h b/fs/cifs/smbdirect.h
> index a87fca82a796..7003722ab004 100644
> --- a/fs/cifs/smbdirect.h
> +++ b/fs/cifs/smbdirect.h
> @@ -226,7 +226,7 @@ struct smbd_buffer_descriptor_v1 {
> } __packed;
>
> /* Default maximum number of SGEs in a RDMA send/recv */
> -#define SMBDIRECT_MAX_SGE 16
> +#define SMBDIRECT_MAX_SGE 6
> /* The context for a SMBD request */
> struct smbd_request {
> struct smbd_connection *info;
> diff --git a/fs/ksmbd/transport_rdma.c b/fs/ksmbd/transport_rdma.c
> index e646d79554b8..70662b3bd590 100644
> --- a/fs/ksmbd/transport_rdma.c
> +++ b/fs/ksmbd/transport_rdma.c
> @@ -42,7 +42,7 @@
> /* SMB_DIRECT negotiation timeout in seconds */
> #define SMB_DIRECT_NEGOTIATE_TIMEOUT 120
>
> -#define SMB_DIRECT_MAX_SEND_SGES 8
> +#define SMB_DIRECT_MAX_SEND_SGES 6
> #define SMB_DIRECT_MAX_RECV_SGES 1
>
> /*
With that, iWarp works for me. You can add:
Tested-by: David Howells <dhowells@redhat.com>
next prev parent reply other threads:[~2022-05-25 9:30 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 [this message]
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=1922487.1653470999@warthog.procyon.org.uk \
--to=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 \
--cc=tom@talpey.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