linux-cifs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve French <smfrench@gmail.com>
To: Hyunchul Lee <hyc.lee@gmail.com>
Cc: Namjae Jeon <linkinjeon@kernel.org>,
	Sergey Senozhatsky <senozhatsky@chromium.org>,
	CIFS <linux-cifs@vger.kernel.org>
Subject: Re: [PATCH 2/2] ksmbd: smbd: change the default maximum read/write, receive size
Date: Sun, 9 Jan 2022 19:43:30 -0600	[thread overview]
Message-ID: <CAH2r5msGLvF4-9h2TXxCrYXsEXvLtVoRyY77PXxzE3MeP_vKHQ@mail.gmail.com> (raw)
In-Reply-To: <CANFS6baREfEidN+FqZROiF+6QtOQ6FXae6f0L9EVKaUFK2L3hg@mail.gmail.com>

I was concerned because I saw significant improvements in large i/o
(file copy to or from the server) to Windows and Azure going to 1MB
(negotiated max read/write size), then slightly better to 2MB and
slightly better still to 4MB (was hard to show gain with 8MB in my
earlier tests though)

On Sun, Jan 9, 2022 at 7:37 PM Hyunchul Lee <hyc.lee@gmail.com> wrote:
>
> 2022년 1월 9일 (일) 오후 9:56, Namjae Jeon <linkinjeon@kernel.org>님이 작성:
> >
> > 2022-01-09 15:44 GMT+09:00, Steve French <smfrench@gmail.com>:
> > > Do you have more detail on what the negotiated readsize/writesize
> > > would be for Windows clients with this size? for Linux clients?
> > Hyunchul, Please answer.
> >
>
> For a Linux client, if connected using smb-direct,
> the size will be 1048512. But connected with multichannel,
> the size will be 4MB instead of 1048512. And this causes
> problems because the read/write size is bigger than 1048512.
> It looks like a bug. I have to limit the ksmbd's SMB2 maximum
> read/write size for a test.
>
> For Windows clients, the actual read/write size is less than
> 1048512.
>
> > >
> > > It looked like it would still be 4MB at first glance (although in
> > > theory some Windows could do 8MB) ... I may have missed something
> > I understood that multiple-buffer descriptor support was required to
> > set a read/write size of 1MB or more. As I know, Hyunchul is currently
> > working on it.
> > It seems to be set to the smaller of max read/write size in smb-direct
> > negotiate and max read/write size in smb2 negotiate.
> >
> > Hyunchul, I have one question more, How did you get 1048512 setting value ?
> > >
>
> I remember when the size was 1MB, Windows clients requested read/write with
> 1048512 and 64.
>
> > > On Sat, Jan 8, 2022 at 8:43 PM Namjae Jeon <linkinjeon@kernel.org> wrote:
> > >>
> > >> 2022-01-07 14:45 GMT+09:00, Hyunchul Lee <hyc.lee@gmail.com>:
> > >> > Due to restriction that cannot handle multiple
> > >> > buffer descriptor structures, decrease the maximum
> > >> > read/write size for Windows clients.
> > >> >
> > >> > And set the maximum fragmented receive size
> > >> > in consideration of the receive queue size.
> > >> >
> > >> > Signed-off-by: Hyunchul Lee <hyc.lee@gmail.com>
> > >> Acked-by: Namjae Jeon <linkinjeon@kernel.org>
> > >
> > >
> > >
> > > --
> > > Thanks,
> > >
> > > Steve
> > >
>
>
>
> --
> Thanks,
> Hyunchul



-- 
Thanks,

Steve

  reply	other threads:[~2022-01-10  1:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07  5:45 [PATCH 1/2] ksmbd: smbd: create MR pool Hyunchul Lee
2022-01-07  5:45 ` [PATCH 2/2] ksmbd: smbd: change the default maximum read/write, receive size Hyunchul Lee
2022-01-09  2:43   ` Namjae Jeon
2022-01-09  6:44     ` Steve French
2022-01-09 12:56       ` Namjae Jeon
2022-01-10  1:37         ` Hyunchul Lee
2022-01-10  1:43           ` Steve French [this message]
2022-01-10  4:03             ` Hyunchul Lee
2022-01-17 23:33           ` Namjae Jeon
2022-01-18  6:40             ` Hyunchul Lee
2022-01-09  2:42 ` [PATCH 1/2] ksmbd: smbd: create MR pool Namjae Jeon

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=CAH2r5msGLvF4-9h2TXxCrYXsEXvLtVoRyY77PXxzE3MeP_vKHQ@mail.gmail.com \
    --to=smfrench@gmail.com \
    --cc=hyc.lee@gmail.com \
    --cc=linkinjeon@kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=senozhatsky@chromium.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;
as well as URLs for NNTP newsgroup(s).