public inbox for linux-cifs@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Namjae Jeon <linkinjeon@kernel.org>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
	linux-cifs@vger.kernel.org, smfrench@gmail.com, tom@talpey.com,
	atteh.mailbox@gmail.com, Steve French <stfrench@microsoft.com>
Subject: Re: [PATCH] ksmbd: don't terminate inactive sessions after a few seconds
Date: Fri, 24 Mar 2023 14:45:29 +0900	[thread overview]
Message-ID: <20230324054529.GG3271889@google.com> (raw)
In-Reply-To: <CAKYAXd_y+xh_2Rp9RLi1xWfrsgYSBvQENMkE0uS=W1Wnp6Espg@mail.gmail.com>

On (23/03/24 13:28), Namjae Jeon wrote:
> > By the way, ksmbd_tcp_readv() calls kvec_array_init() on each iteration.
> > Shouldn't we call it only if length > 0? That is only if the most recent
> > call to kernel_recvmsg() has read some data.
> If length == to_read is equal then it is not called. And in case
> length < to_read, we have to call it which reinitialize io vec again
> for reading the rest of the data.

What I'm saying is: if length == 0 on the previous iteration then
we don't need to kvec_array_init(). But maybe I'm missing something.

  reply	other threads:[~2023-03-24  5:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-21 13:33 [PATCH] ksmbd: don't terminate inactive sessions after a few seconds Namjae Jeon
2023-03-21 13:33 ` [PATCH] ksmbd: return STATUS_NOT_SUPPORTED on unsupported smb2.0 dialect Namjae Jeon
2023-03-21 13:33 ` [PATCH] ksmbd: return unsupported error on smb1 mount Namjae Jeon
2023-03-23  2:53   ` Sergey Senozhatsky
2023-03-23  4:10     ` Namjae Jeon
2023-03-23  5:00       ` Sergey Senozhatsky
2023-03-23  5:04         ` Namjae Jeon
2023-03-23  5:17           ` [PATCH v2] " Namjae Jeon
2023-03-24  3:44             ` Sergey Senozhatsky
2023-03-24  3:50 ` [PATCH] ksmbd: don't terminate inactive sessions after a few seconds Sergey Senozhatsky
2023-03-24  4:28   ` Namjae Jeon
2023-03-24  5:45     ` Sergey Senozhatsky [this message]
2023-03-24  7:00       ` Namjae Jeon
2023-03-24  5:43 ` Sergey Senozhatsky

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=20230324054529.GG3271889@google.com \
    --to=senozhatsky@chromium.org \
    --cc=atteh.mailbox@gmail.com \
    --cc=linkinjeon@kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=smfrench@gmail.com \
    --cc=stfrench@microsoft.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