All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Talpey <tom@talpey.com>
To: Steve French <smfrench@gmail.com>
Cc: linux-cifs@vger.kernel.org, linkinjeon@kernel.org,
	senozhatsky@chromium.org, bmt@zurich.ibm.com
Subject: Re: [RFC PATCH 0/6] Reduce SMBDirect RDMA SGE counts and sizes
Date: Thu, 22 Sep 2022 15:35:37 -0400	[thread overview]
Message-ID: <c68dd87d-0c42-2673-6467-e1063c4fa9a3@talpey.com> (raw)
In-Reply-To: <CAH2r5muhROptfZ+fUjhCfwzoeJqNku4Nkpjv63N5WTdhpEWWoA@mail.gmail.com>

[ Resending to fix the missing "vger."! ]

On 9/20/2022 9:58 PM, Steve French wrote:
> are these still current?

Hi Steve, yes these are current. As you know we were going to add
siw-based RDMA testing to the buildbot during last week's IOLab,
but we didn't get the chance. And this week, I've been forced to
self-isolate and I therefore have had no chance to test further.

Here's the deal:

1) The changes are tested by me as described in the message. They
passed all my confidence checks, including artificially reducing
SGEs all the way down to 2.

2) But, I haven't seen any reviews, or anyone testing.

3) I won't be very productive until next week, assuming I feel better.
I'll be back on it as soon as I can.

4) Because neither client nor server ever worked over softiWARP before,
the patches shouldn't go to stable.

5) Because they only address RDMA operation, they won't break ordinary
users.

Your call.

Tom.


> On Tue, Sep 13, 2022 at 5:04 PM Tom Talpey <tom@talpey.com> wrote:
>>
>> Allocate fewer SGEs and standard packet sizes in both kernel SMBDirect
>> implementations.
>>
>> The current maximum values (16 SGEs and 8192 bytes) cause failures on the
>> SoftiWARP provider, and are suboptimal on others. Reduce these to 6 and
>> 1364. Additionally, recode smbd_send() to work with as few as 2 SGEs,
>> and for debug sanity, reformat client-side logging to more clearly show
>> addresses, lengths and flags in the appropriate base.
>>
>> Tested over SoftiWARP and SoftRoCE with shell, Connectathon basic and general,
>> and to be tested with XFStests here at SMB3 IOLab this week.
>>
>> Tom Talpey (6):
>>    Decrease the number of SMB3 smbdirect client SGEs
>>    Decrease the number of SMB3 smbdirect server SGEs
>>    Reduce client smbdirect max receive segment size
>>    Reduce server smbdirect max send/receive segment sizes
>>    Handle variable number of SGEs in client smbdirect send.
>>    Fix formatting of client smbdirect RDMA logging
>>
>>   fs/cifs/smbdirect.c       | 227 ++++++++++++++++----------------------
>>   fs/cifs/smbdirect.h       |  14 ++-
>>   fs/ksmbd/transport_rdma.c |   6 +-
>>   3 files changed, 109 insertions(+), 138 deletions(-)
>>
>> --
>> 2.34.1
>>
> 
> 

      parent reply	other threads:[~2022-09-22 19:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-13 22:19 [RFC PATCH 0/6] Reduce SMBDirect RDMA SGE counts and sizes Tom Talpey
2022-09-13 22:19 ` [PATCH 1/6] Decrease the number of SMB3 smbdirect client SGEs Tom Talpey
2022-09-13 22:19 ` [PATCH 2/6] Decrease the number of SMB3 smbdirect server SGEs Tom Talpey
2022-09-13 22:19 ` [PATCH 3/6] Reduce client smbdirect max receive segment size Tom Talpey
2022-09-13 22:19 ` [PATCH 4/6] Reduce server smbdirect max send/receive segment sizes Tom Talpey
2022-09-13 22:19 ` [PATCH 5/6] Handle variable number of SGEs in client smbdirect send Tom Talpey
2022-09-13 22:19 ` [PATCH 6/6] Fix formatting of client smbdirect RDMA logging Tom Talpey
     [not found] ` <CAH2r5muhROptfZ+fUjhCfwzoeJqNku4Nkpjv63N5WTdhpEWWoA@mail.gmail.com>
2022-09-22 19:35   ` Tom Talpey [this message]

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=c68dd87d-0c42-2673-6467-e1063c4fa9a3@talpey.com \
    --to=tom@talpey.com \
    --cc=bmt@zurich.ibm.com \
    --cc=linkinjeon@kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=senozhatsky@chromium.org \
    --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 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.