Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: aman1cifs@gmail.com
To: linux-cifs@vger.kernel.org, sfrench@samba.org, pc@manguebit.com,
	sprasad@microsoft.com, tom@talpey.com, ronniesahlberg@gmail.com,
	bharathsm@microsoft.com, psachdeva@microsoft.com
Cc: Aman <aman1@microsoft.com>
Subject: [PATCH 1/2] CIFS: Propagate min offload along with other parameters from primary to secondary channels.
Date: Fri, 28 Mar 2025 06:13:12 +0000	[thread overview]
Message-ID: <20250328061312.3043039-1-aman1cifs@gmail.com> (raw)
In-Reply-To: <Z66BwJnHAI8zDOzP@linuxbox.oloxx3b4wsrernbskgt3tooxxe.gx.internal.cloudapp.net>

From: Aman <aman1@microsoft.com>

In a multichannel setup, it was observed that a few fields were not being
copied over to the secondary channels, which impacted performance in cases
where these options were relevant but not properly synchronized. To address
this, this patch introduces copying the following parameters from the
primary channel to the secondary channels:

- min_offload
- retrans

By copying these parameters, we ensure consistency across channels and
prevent performance degradation due to missing or outdated settings.

Signed-off-by: Aman <aman1@microsoft.com>
---
 fs/smb/client/sess.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/fs/smb/client/sess.c b/fs/smb/client/sess.c
index 91d4d409c..35ae7ad3b 100644
--- a/fs/smb/client/sess.c
+++ b/fs/smb/client/sess.c
@@ -522,6 +522,8 @@ cifs_ses_add_channel(struct cifs_ses *ses,
 	ctx->sockopt_tcp_nodelay = ses->server->tcp_nodelay;
 	ctx->echo_interval = ses->server->echo_interval / HZ;
 	ctx->max_credits = ses->server->max_credits;
+	ctx->min_offload = ses->server->min_offload;
+	ctx->retrans = ses->server->retrans;
 
 	/*
 	 * This will be used for encoding/decoding user/domain/pw
-- 
2.43.0


       reply	other threads:[~2025-03-28  6:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Z66BwJnHAI8zDOzP@linuxbox.oloxx3b4wsrernbskgt3tooxxe.gx.internal.cloudapp.net>
2025-03-28  6:13 ` aman1cifs [this message]
2025-03-28  7:19   ` [PATCH 1/2] CIFS: Propagate min offload along with other parameters from primary to secondary channels Shyam Prasad N
     [not found]   ` <CAH2r5mtmHNisb91cr4jSBjuTRJp-J2DOHDaYmSRTM8MbdKEG_g@mail.gmail.com>
2025-03-30  3:58     ` Fwd: " Steve French
2025-02-14 12:43 aman1cifs
2025-02-27 16:33 ` Paulo Alcantara
2025-03-06 17:46 ` aman1cifs
2025-03-11  3:25   ` Steve French
2025-03-11 11:21     ` aman

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=20250328061312.3043039-1-aman1cifs@gmail.com \
    --to=aman1cifs@gmail.com \
    --cc=aman1@microsoft.com \
    --cc=bharathsm@microsoft.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=pc@manguebit.com \
    --cc=psachdeva@microsoft.com \
    --cc=ronniesahlberg@gmail.com \
    --cc=sfrench@samba.org \
    --cc=sprasad@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