Reduce SMBDirect RDMA SGE counts and sizes
Subsystems (2)
Tom Talpey
reviewerv2 cover Reduce SMBDirect RDMA SGE counts and sizes
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.
v2: correct an uninitialized value issue found by Coverity
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(-)
Signature · 1 line
2.34.1
Tom Talpey
reviewerPATCH v2 1/6 Decrease the number of SMB3 smbdirect client SGEs
The client-side SMBDirect layer requires no more than 6 send SGEs and 1 receive SGE. The previous default of 8 send and 8 receive causes smbdirect to fail on the SoftiWARP (siw) provider, and possibly others. Additionally, large numbers of SGEs reduces performance significantly on adapter implementations.
Also correct the frmr page count comment (not an SGE count).
--- fs/cifs/smbdirect.c | 26 ++++++++++++-------------- fs/cifs/smbdirect.h | 14 +++++++++----- 2 files changed, 21 insertions(+), 19 deletions(-)
fs/cifs/smbdirect.c +12 -14
@@ -99,7 +99,7 @@ int smbd_keep_alive_interval = 120;* User configurable initial values for RDMA transport * The actual values used may be lower and are limited to hardware capabilities */ -/* Default maximum number of SGEs in a RDMA write/read */ +/* Default maximum number of pages in a single RDMA write/read */ int smbd_max_frmr_depth =2048 ;/* If payload is less than this byte, use RDMA send/recv not read/write */
@@ -1017,9 +1017,9 @@ static int smbd_post_send_data( {int i;u32 data_length =0 ; -struct scatterlist sgl[SMBDIRECT_MAX_SGE ]; +struct scatterlist sgl[SMBDIRECT_MAX_SEND_SGE -1 ]; -if (n_vec >SMBDIRECT_MAX_SGE ) { +if (n_vec >SMBDIRECT_MAX_SEND_SGE -1 ) {cifs_dbg (VFS ,"Can't fit data to SGL, n_vec=%d\n" , n_vec);return -EINVAL ; }
@@ -1562,17 +1562,15 @@ static struct smbd_connection *_smbd_get_connection( info->max_receive_size = smbd_max_receive_size; info->keep_alive_interval = smbd_keep_alive_interval; -if (info->id->device->attrs.max_send_sge <SMBDIRECT_MAX_SGE ) { +if (info->id->device->attrs.max_send_sge <SMBDIRECT_MAX_SEND_SGE || + info->id->device->attrs.max_recv_sge <SMBDIRECT_MAX_RECV_SGE ) {log_rdma_event (ERR , -"warning: device max_send_sge = %d too small\n" , - info->id->device->attrs.max_send_sge); -log_rdma_event (ERR ,"Queue Pair creation may fail\n" ); - } -if (info->id->device->attrs.max_recv_sge <SMBDIRECT_MAX_SGE ) { -log_rdma_event (ERR , -"warning: device max_recv_sge = %d too small\n" , +"device %.*s max_send_sge/max_recv_sge = %d/%d too small\n" , +IB_DEVICE_NAME_MAX , + info->id->device->name, + info->id->device->attrs.max_send_sge, info->id->device->attrs.max_recv_sge); -log_rdma_event (ERR ,"Queue Pair creation may fail\n" ); + goto config_failed; } info->send_cq =NULL ;
@@ -1598,8 +1596,8 @@ static struct smbd_connection *_smbd_get_connection( qp_attr.qp_context = info; qp_attr.cap.max_send_wr = info->send_credit_target; qp_attr.cap.max_recv_wr = info->receive_credit_max; - qp_attr.cap.max_send_sge =SMBDIRECT_MAX_SGE ; - qp_attr.cap.max_recv_sge =SMBDIRECT_MAX_SGE ; + qp_attr.cap.max_send_sge =SMBDIRECT_MAX_SEND_SGE ; + qp_attr.cap.max_recv_sge =SMBDIRECT_MAX_RECV_SGE ; qp_attr.cap.max_inline_data =0 ; qp_attr.sq_sig_type =IB_SIGNAL_REQ_WR ; qp_attr.qp_type =IB_QPT_RC ;
fs/cifs/smbdirect.h +9 -5
@@ -91,7 +91,7 @@ struct smbd_connection {/* Memory registrations */ /* Maximum number of RDMA read/write outstanding on this connection */ int responder_resources; -/* Maximum number of SGEs in a RDMA write/read */ +/* Maximum number of pages in a single RDMA write/read on this connection */ int max_frmr_depth;/* * If payload is less than or equal to the threshold,
@@ -225,21 +225,25 @@ struct smbd_buffer_descriptor_v1 {__le32 length; } __packed; -/* Default maximum number of SGEs in a RDMA send/recv */ -#define SMBDIRECT_MAX_SGE 16 +/* Maximum number of SGEs used by smbdirect.c in any send work request */ +#define SMBDIRECT_MAX_SEND_SGE 6 +/* The context for a SMBD request */ struct smbd_request {struct smbd_connection *info;struct ib_cqe cqe; -/* the SGE entries for this packet */ -struct ib_sge sge[SMBDIRECT_MAX_SGE ]; +/* the SGE entries for this work request */ +struct ib_sge sge[SMBDIRECT_MAX_SEND_SGE ];int num_sge;/* SMBD packet header follows this structure */ u8 packet[]; }; +/* Maximum number of SGEs used by smbdirect.c in any receive work request */ +#define SMBDIRECT_MAX_RECV_SGE 1 +/* The context for a SMBD response */ struct smbd_response {struct smbd_connection *info;
Signature · 1 line
2.34.1
Tom Talpey
reviewerPATCH v2 2/6 Decrease the number of SMB3 smbdirect server SGEs
In reply to Tom TalpeyThe server-side SMBDirect layer requires no more than 6 send SGEs The previous default of 8 causes ksmbd to fail on the SoftiWARP (siw) provider, and possibly others. Additionally, large numbers of SGEs reduces performance significantly on adapter implementations.
--- fs/ksmbd/transport_rdma.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/ksmbd/transport_rdma.c +1 -1
@@ -32,7 +32,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/*
Signature · 1 line
2.34.1
Re: [PATCH v2 2/6] Decrease the number of SMB3 smbdirect server SGEs
2022-09-24 6:53 GMT+09:00, Tom Talpey <[email protected]>:
Quoted 6 lines
The server-side SMBDirect layer requires no more than 6 send SGEs The previous default of 8 causes ksmbd to fail on the SoftiWARP (siw) provider, and possibly others. Additionally, large numbers of SGEs reduces performance significantly on adapter implementations.
Signed-off-by Tom Talpey <[email protected]>
Thanks!
Tom Talpey
reviewerPATCH v2 3/6 Reduce client smbdirect max receive segment size
In reply to Tom TalpeyReduce client smbdirect max segment receive size to 1364 to match protocol norms. Larger buffers are unnecessary and add significant memory overhead.
--- fs/cifs/smbdirect.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/cifs/smbdirect.c +1 -1
@@ -90,7 +90,7 @@ int smbd_max_send_size = 1364;int smbd_max_fragmented_recv_size =1024 *1024 ;/* The maximum single-message size which can be received */ -int smbd_max_receive_size =8192 ; +int smbd_max_receive_size =1364 ;/* The timeout to initiate send of a keepalive message on idle */ int smbd_keep_alive_interval =120 ;
Signature · 1 line
2.34.1
Tom Talpey
reviewerPATCH v2 4/6 Reduce server smbdirect max send/receive segment sizes
In reply to Tom TalpeyReduce ksmbd smbdirect max segment send and receive size to 1364 to match protocol norms. Larger buffers are unnecessary and add significant memory overhead.
--- fs/ksmbd/transport_rdma.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
fs/ksmbd/transport_rdma.c +2 -2
@@ -62,13 +62,13 @@ static int smb_direct_receive_credit_max = 255;static int smb_direct_send_credit_target =255 ;/* The maximum single message size can be sent to remote peer */ -static int smb_direct_max_send_size =8192 ; +static int smb_direct_max_send_size =1364 ;/* The maximum fragmented upper-layer payload receive size supported */ static int smb_direct_max_fragmented_recv_size =1024 *1024 ;/* The maximum single-message size which can be received */ -static int smb_direct_max_receive_size =8192 ; +static int smb_direct_max_receive_size =1364 ;static int smb_direct_max_read_write_size =SMBD_DEFAULT_IOSIZE ;
Signature · 1 line
2.34.1
Namjae Jeon
maintainerRe: [PATCH v2 4/6] Reduce server smbdirect max send/receive segment sizes
2022-09-24 6:53 GMT+09:00, Tom Talpey <[email protected]>:
Quoted 16 lines
Reduce ksmbd smbdirect max segment send and receive size to 1364 to match protocol norms. Larger buffers are unnecessary and add significant memory overhead.
Signed-off-by Tom Talpey <[email protected]>--- fs/ksmbd/transport_rdma.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)fs/ksmbd/transport_rdma.c +0
-0@@ -62,13 +62,13 @@ static int smb_direct_receive_credit_max = 255;static int smb_direct_send_credit_target =255 ;
fs/ksmbd/transport_rdma.c static int smb_direct_receive_credit_max = 255; · line 71
Quoted 10 lines
fs/ksmbd/transport_rdma.c +2
-2/* The maximum single message size can be sent to remote peer */ -static int smb_direct_max_send_size =8192 ; +static int smb_direct_max_send_size =1364 ;/* The maximum fragmented upper-layer payload receive size supported */ static int smb_direct_max_fragmented_recv_size =1024 *1024 ;/* The maximum single-message size which can be received */ -static int smb_direct_max_receive_size =8192 ; +static int smb_direct_max_receive_size =1364 ;
Can I know what value windows server set to ?
I can see the following settings for them in MS-SMBD.pdf Connection.MaxSendSize is set to 1364. Connection.MaxReceiveSize is set to 8192.
Why does the specification describe setting it to 8192?
Quoted 7 lines
fs/ksmbd/transport_rdma.c +0
-1static int smb_direct_max_read_write_size =SMBD_DEFAULT_IOSIZE ; --2.34.1
Tom Talpey
reviewerRe: [PATCH v2 4/6] Reduce server smbdirect max send/receive segment sizes
Quoted 24 lines · Namjae Jeon
2022-09-24 6:53 GMT+09:00, Tom Talpey <[email protected]>:
Quoted 23 lines
Reduce ksmbd smbdirect max segment send and receive size to 1364 to match protocol norms. Larger buffers are unnecessary and add significant memory overhead.
Signed-off-by Tom Talpey <[email protected]>--- fs/ksmbd/transport_rdma.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)fs/ksmbd/transport_rdma.c +1
-1@@ -62,13 +62,13 @@ static int smb_direct_receive_credit_max = 255;static int smb_direct_send_credit_target =255 ;/* The maximum single message size can be sent to remote peer */ -static int smb_direct_max_send_size =8192 ; +static int smb_direct_max_send_size =1364 ;/* The maximum fragmented upper-layer payload receive size supported */ static int smb_direct_max_fragmented_recv_size =1024 *1024 ;
Quoted 8 lines
fs/ksmbd/transport_rdma.c static int smb_direct_receive_credit_max = 255; · line 71
Quoted 3 lines
fs/ksmbd/transport_rdma.c +1
-1/* The maximum single-message size which can be received */ -static int smb_direct_max_receive_size =8192 ; +static int smb_direct_max_receive_size =1364 ;Can I know what value windows server set to ?
I can see the following settings for them in MS-SMBD.pdf Connection.MaxSendSize is set to 1364. Connection.MaxReceiveSize is set to 8192.
Glad you asked, it's an interesting situation IMO.
In MS-SMBD, the following are documented as behavior notes:
Client-side (active connect):
Connection.MaxSendSize is set to 1364.
Connection.MaxReceiveSize is set to 8192.
Server-side (passive listen):
Connection.MaxSendSize is set to 1364.
Connection.MaxReceiveSize is set to 8192.
However, these are only the initial values. During SMBD negotiation, the two sides adjust downward to the other's maximum. Therefore, Windows connecting to Windows will use 1364 on both sides.
In cifs and ksmbd, the choices were messier:
Client-side smbdirect.c:
int smbd_max_send_size = 1364;
int smbd_max_receive_size = 8192;
Server-side transport_rdma.c:
static int smb_direct_max_send_size = 8192;
static int smb_direct_max_receive_size = 8192;
Therefore, peers connecting to ksmbd would typically end up negotiating 1364 for send and 8192 for receive.
There is almost no good reason to use larger buffers. Because RDMA is highly efficient, and the smbdirect protocol trivially fragments longer messages, there is no significant performance penalty.
And, because not many SMB3 messages require 8192 bytes over smbdirect, it's a colossal waste of virtually contiguous kernel memory to allocate 8192 to all receives.
By setting all four to the practical reality of 1364, it's a consistent and efficient default, and aligns Linux smbdirect with Windows.
Tom.
Quoted 10 lines
Why does the specification describe setting it to 8192?
Quoted 7 lines
fs/ksmbd/transport_rdma.c +0
-1static int smb_direct_max_read_write_size =SMBD_DEFAULT_IOSIZE ; --2.34.1
Namjae Jeon
maintainerRe: [PATCH v2 4/6] Reduce server smbdirect max send/receive segment sizes
2022-09-26 0:41 GMT+09:00, Tom Talpey <[email protected]>:
Quoted 70 lines · Namjae Jeon
Quoted 25 lines
2022-09-24 6:53 GMT+09:00, Tom Talpey <[email protected]>:
Quoted 24 lines
Reduce ksmbd smbdirect max segment send and receive size to 1364 to match protocol norms. Larger buffers are unnecessary and add significant memory overhead.
Signed-off-by Tom Talpey <[email protected]>--- fs/ksmbd/transport_rdma.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)fs/ksmbd/transport_rdma.c +1
-1@@ -62,13 +62,13 @@ static int smb_direct_receive_credit_max = 255;static int smb_direct_send_credit_target =255 ;/* The maximum single message size can be sent to remote peer */ -static int smb_direct_max_send_size =8192 ; +static int smb_direct_max_send_size =1364 ;/* The maximum fragmented upper-layer payload receive size supported */ static int smb_direct_max_fragmented_recv_size =1024 *1024 ;Quoted 8 lines
fs/ksmbd/transport_rdma.c static int smb_direct_receive_credit_max = 255; · line 71
Quoted 3 lines
fs/ksmbd/transport_rdma.c +1
-1/* The maximum single-message size which can be received */ -static int smb_direct_max_receive_size =8192 ; +static int smb_direct_max_receive_size =1364 ;Can I know what value windows server set to ?
I can see the following settings for them in MS-SMBD.pdf Connection.MaxSendSize is set to 1364. Connection.MaxReceiveSize is set to 8192.
Glad you asked, it's an interesting situation IMO.
In MS-SMBD, the following are documented as behavior notes:
Client-side (active connect):
Connection.MaxSendSize is set to 1364.
Connection.MaxReceiveSize is set to 8192.Server-side (passive listen):
Connection.MaxSendSize is set to 1364.
Connection.MaxReceiveSize is set to 8192.However, these are only the initial values. During SMBD negotiation, the two sides adjust downward to the other's maximum. Therefore, Windows connecting to Windows will use 1364 on both sides.
In cifs and ksmbd, the choices were messier:
Client-side
smbdirect.c:
intsmbd_max_send_size= 1364;
intsmbd_max_receive_size= 8192;Server-side
transport_rdma.c:
static intsmb_direct_max_send_size= 8192;
static intsmb_direct_max_receive_size= 8192;Therefore, peers connecting to ksmbd would typically end up negotiating 1364 for send and 8192 for receive.
There is almost no good reason to use larger buffers. Because RDMA is highly efficient, and the smbdirect protocol trivially fragments longer messages, there is no significant performance penalty.
Quoted 7 lines
And, because not many SMB3 messages require 8192 bytes over smbdirect, it's a colossal waste of virtually contiguous kernel memory to allocate 8192 to all receives.
By setting all four to the practical reality of 1364, it's a consistent and efficient default, and aligns Linux smbdirect with Windows.
Thanks for your detailed explanation! Agree to set both to 1364 by default, Is there any usage to increase it? I wonder if users need any configuration parameters to adjust them.
Quoted 14 lines
Tom.
Quoted 10 lines
Why does the specification describe setting it to 8192?
Quoted 7 lines
fs/ksmbd/transport_rdma.c +0
-1static int smb_direct_max_read_write_size =SMBD_DEFAULT_IOSIZE ; --2.34.1
Tom Talpey
reviewerRe: [PATCH v2 4/6] Reduce server smbdirect max send/receive segment sizes
Quoted 75 lines · Namjae Jeon
2022-09-26 0:41 GMT+09:00, Tom Talpey <[email protected]>:
Quoted 74 lines · Namjae Jeon
Quoted 25 lines
2022-09-24 6:53 GMT+09:00, Tom Talpey <[email protected]>:
Quoted 24 lines
Reduce ksmbd smbdirect max segment send and receive size to 1364 to match protocol norms. Larger buffers are unnecessary and add significant memory overhead.
Signed-off-by Tom Talpey <[email protected]>--- fs/ksmbd/transport_rdma.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)fs/ksmbd/transport_rdma.c +1
-1@@ -62,13 +62,13 @@ static int smb_direct_receive_credit_max = 255;static int smb_direct_send_credit_target =255 ;/* The maximum single message size can be sent to remote peer */ -static int smb_direct_max_send_size =8192 ; +static int smb_direct_max_send_size =1364 ;/* The maximum fragmented upper-layer payload receive size supported */ static int smb_direct_max_fragmented_recv_size =1024 *1024 ;Quoted 8 lines
fs/ksmbd/transport_rdma.c static int smb_direct_receive_credit_max = 255; · line 71
Quoted 3 lines
fs/ksmbd/transport_rdma.c +1
-1/* The maximum single-message size which can be received */ -static int smb_direct_max_receive_size =8192 ; +static int smb_direct_max_receive_size =1364 ;Can I know what value windows server set to ?
I can see the following settings for them in MS-SMBD.pdf Connection.MaxSendSize is set to 1364. Connection.MaxReceiveSize is set to 8192.
Glad you asked, it's an interesting situation IMO.
In MS-SMBD, the following are documented as behavior notes:
Client-side (active connect):
Connection.MaxSendSize is set to 1364.
Connection.MaxReceiveSize is set to 8192.Server-side (passive listen):
Connection.MaxSendSize is set to 1364.
Connection.MaxReceiveSize is set to 8192.However, these are only the initial values. During SMBD negotiation, the two sides adjust downward to the other's maximum. Therefore, Windows connecting to Windows will use 1364 on both sides.
In cifs and ksmbd, the choices were messier:
Client-side
smbdirect.c:int smbd_max_send_size = 1364; int smbd_max_receive_size = 8192;Server-side
transport_rdma.c:static int smb_direct_max_send_size = 8192; static int smb_direct_max_receive_size = 8192;Therefore, peers connecting to ksmbd would typically end up negotiating 1364 for send and 8192 for receive.
There is almost no good reason to use larger buffers. Because RDMA is highly efficient, and the smbdirect protocol trivially fragments longer messages, there is no significant performance penalty.
And, because not many SMB3 messages require 8192 bytes over smbdirect, it's a colossal waste of virtually contiguous kernel memory to allocate 8192 to all receives.
Quoted 6 lines
Quoted 3 lines
By setting all four to the practical reality of 1364, it's a consistent and efficient default, and aligns Linux smbdirect with Windows.
Thanks for your detailed explanation! Agree to set both to 1364 by default, Is there any usage to increase it? I wonder if users need any configuration parameters to adjust them.
In my opinion, probably not. I give some reasons why large fragments aren't always helpful just above. It's the same number of packets! Just a question of whether SMBDirect or Ethernet does the fragmentation, and the buffer management.
There might conceivably be a case for *smaller*, for example on IB when it's cranked down to the minimum (256B) MTU. But it will work with this default.
I'd say let's don't over-engineer it until we address the many other issues in this code. Merging the two smbdirect implementations is much more important than adding tweaky little knobs to both. MHO.
Tom.
Quoted 12 lines
Quoted 11 lines
Quoted 10 lines
Why does the specification describe setting it to 8192?
Quoted 7 lines
fs/ksmbd/transport_rdma.c +0
-1static int smb_direct_max_read_write_size =SMBD_DEFAULT_IOSIZE ; --2.34.1
RE: Re: [PATCH v2 4/6] Reduce server smbdirect max send/receive segment sizes
Quoted 92 lines
-----Original Message-----
From: Tom Talpey <[email protected]>
Sent: Monday, 26 September 2022 19:25
To: Namjae Jeon <[email protected]>
Cc: [email protected]; [email protected]; [email protected]; Bernard Metzler <[email protected]>; [email protected]; [email protected]
Subject: [EXTERNAL] Re: [PATCH v2 4/6] Reduce server smbdirect max send/receive segment sizesQuoted 19 lines · Namjae Jeon
2022-09-26 0:41 GMT+09:00, Tom Talpey <[email protected]>:
Quoted 18 lines · Namjae Jeon
Quoted 17 lines
2022-09-24 6:53 GMT+09:00, Tom Talpey <[email protected]>:
Quoted 16 lines
Reduce ksmbd smbdirect max segment send and receive size to 1364 to match protocol norms. Larger buffers are unnecessary and add significant memory overhead.
Signed-off-by Tom Talpey <[email protected]>--- fs/ksmbd/transport_rdma.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)fs/ksmbd/transport_rdma.c +0
-0@@ -62,13 +62,13 @@ static int smb_direct_receive_credit_max = 255;static int smb_direct_send_credit_target =255 ;Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
fs/ksmbd/transport_rdma.c static int smb_direct_receive_credit_max = 255;
Quoted 5 lines
fs/ksmbd/transport_rdma.c +1
-1/* The maximum single message size can be sent to remote peer */ -static int smb_direct_max_send_size =8192 ; +static int smb_direct_max_send_size =1364 ;/* The maximum fragmented upper-layer payload receive size supported
Quoted 54 lines
Quoted 54 lines
Quoted 11 lines
fs/ksmbd/transport_rdma.c static int smb_direct_receive_credit_max = 255; · line 71
Quoted 6 lines
fs/ksmbd/transport_rdma.c +1
-1*/ static int smb_direct_max_fragmented_recv_size =1024 *1024 ;/* The maximum single-message size which can be received */ -static int smb_direct_max_receive_size =8192 ; +static int smb_direct_max_receive_size =1364 ;Can I know what value windows server set to ?
I can see the following settings for them in MS-SMBD.pdf Connection.MaxSendSize is set to 1364. Connection.MaxReceiveSize is set to 8192.
Glad you asked, it's an interesting situation IMO.
In MS-SMBD, the following are documented as behavior notes:
Client-side (active connect):
Connection.MaxSendSize is set to 1364.
Connection.MaxReceiveSize is set to 8192.Server-side (passive listen):
Connection.MaxSendSize is set to 1364.
Connection.MaxReceiveSize is set to 8192.However, these are only the initial values. During SMBD negotiation, the two sides adjust downward to the other's maximum. Therefore, Windows connecting to Windows will use 1364 on both sides.
In cifs and ksmbd, the choices were messier:
Client-side
smbdirect.c:int smbd_max_send_size = 1364; int smbd_max_receive_size = 8192;Server-side
transport_rdma.c:static int smb_direct_max_send_size = 8192; static int smb_direct_max_receive_size = 8192;Therefore, peers connecting to ksmbd would typically end up negotiating 1364 for send and 8192 for receive.
There is almost no good reason to use larger buffers. Because RDMA is highly efficient, and the smbdirect protocol trivially fragments longer messages, there is no significant performance penalty.
And, because not many SMB3 messages require 8192 bytes over smbdirect, it's a colossal waste of virtually contiguous kernel memory to allocate 8192 to all receives.
By setting all four to the practical reality of 1364, it's a consistent and efficient default, and aligns Linux smbdirect with Windows.
Quoted 9 lines
Quoted 3 lines
Thanks for your detailed explanation! Agree to set both to 1364 by default, Is there any usage to increase it? I wonder if users need any configuration parameters to adjust them.
In my opinion, probably not. I give some reasons why large fragments aren't always helpful just above. It's the same number of packets! Just a question of whether SMBDirect or Ethernet does the fragmentation, and the buffer management.
One simple reason for larger buffers I am aware of is running efficiently on software only RDMA providers like siw or rxe. For siw I'd guess we cut to less than half the performance with 1364 bytes buffers. But maybe that is no concern for the setups you have in mind.
Best,
Bernard.
Quoted 22 lines
There might conceivably be a case for *smaller*, for example on IB when it's cranked down to the minimum (256B) MTU. But it will work with this default.
I'd say let's don't over-engineer it until we address the many other issues in this code. Merging the two smbdirect implementations is much more important than adding tweaky little knobs to both. MHO.
Tom.
Quoted 12 lines
Quoted 11 lines
Quoted 10 lines
Why does the specification describe setting it to 8192?
Quoted 7 lines
fs/ksmbd/transport_rdma.c +0
-1static int smb_direct_max_read_write_size =SMBD_DEFAULT_IOSIZE ; --2.34.1
Tom Talpey
reviewerRe: [PATCH v2 4/6] Reduce server smbdirect max send/receive segment sizes
Quoted 102 lines · Bernard Metzler
Quoted 92 lines
-----Original Message-----
From: Tom Talpey <[email protected]>
Sent: Monday, 26 September 2022 19:25
To: Namjae Jeon <[email protected]>
Cc: [email protected]; [email protected]; [email protected]; Bernard Metzler <[email protected]>; [email protected]; [email protected]
Subject: [EXTERNAL] Re: [PATCH v2 4/6] Reduce server smbdirect max send/receive segment sizesQuoted 19 lines · Namjae Jeon
2022-09-26 0:41 GMT+09:00, Tom Talpey <[email protected]>:
Quoted 18 lines · Namjae Jeon
Quoted 17 lines
2022-09-24 6:53 GMT+09:00, Tom Talpey <[email protected]>:
Quoted 16 lines
Reduce ksmbd smbdirect max segment send and receive size to 1364 to match protocol norms. Larger buffers are unnecessary and add significant memory overhead.
Signed-off-by Tom Talpey <[email protected]>--- fs/ksmbd/transport_rdma.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)fs/ksmbd/transport_rdma.c +0
-0@@ -62,13 +62,13 @@ static int smb_direct_receive_credit_max = 255;static int smb_direct_send_credit_target =255 ;Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
fs/ksmbd/transport_rdma.c static int smb_direct_receive_credit_max = 255;
Quoted 5 lines
fs/ksmbd/transport_rdma.c +1
-1/* The maximum single message size can be sent to remote peer */ -static int smb_direct_max_send_size =8192 ; +static int smb_direct_max_send_size =1364 ;/* The maximum fragmented upper-layer payload receive size supported
Quoted 54 lines
Quoted 54 lines
Quoted 11 lines
fs/ksmbd/transport_rdma.c static int smb_direct_receive_credit_max = 255; · line 71
Quoted 6 lines
fs/ksmbd/transport_rdma.c +1
-1*/ static int smb_direct_max_fragmented_recv_size =1024 *1024 ;/* The maximum single-message size which can be received */ -static int smb_direct_max_receive_size =8192 ; +static int smb_direct_max_receive_size =1364 ;Can I know what value windows server set to ?
I can see the following settings for them in MS-SMBD.pdf Connection.MaxSendSize is set to 1364. Connection.MaxReceiveSize is set to 8192.
Glad you asked, it's an interesting situation IMO.
In MS-SMBD, the following are documented as behavior notes:
Client-side (active connect):
Connection.MaxSendSize is set to 1364.
Connection.MaxReceiveSize is set to 8192.Server-side (passive listen):
Connection.MaxSendSize is set to 1364.
Connection.MaxReceiveSize is set to 8192.However, these are only the initial values. During SMBD negotiation, the two sides adjust downward to the other's maximum. Therefore, Windows connecting to Windows will use 1364 on both sides.
In cifs and ksmbd, the choices were messier:
Client-side
smbdirect.c:int smbd_max_send_size = 1364; int smbd_max_receive_size = 8192;Server-side
transport_rdma.c:static int smb_direct_max_send_size = 8192; static int smb_direct_max_receive_size = 8192;Therefore, peers connecting to ksmbd would typically end up negotiating 1364 for send and 8192 for receive.
There is almost no good reason to use larger buffers. Because RDMA is highly efficient, and the smbdirect protocol trivially fragments longer messages, there is no significant performance penalty.
And, because not many SMB3 messages require 8192 bytes over smbdirect, it's a colossal waste of virtually contiguous kernel memory to allocate 8192 to all receives.
By setting all four to the practical reality of 1364, it's a consistent and efficient default, and aligns Linux smbdirect with Windows.
Quoted 9 lines
Quoted 3 lines
Thanks for your detailed explanation! Agree to set both to 1364 by default, Is there any usage to increase it? I wonder if users need any configuration parameters to adjust them.
In my opinion, probably not. I give some reasons why large fragments aren't always helpful just above. It's the same number of packets! Just a question of whether SMBDirect or Ethernet does the fragmentation, and the buffer management.
Quoted 5 lines
One simple reason for larger buffers I am aware of is running efficiently on software only RDMA providers like siw or rxe. For siw I'd guess we cut to less than half the performance with 1364 bytes buffers. But maybe that is no concern for the setups you have in mind.
I'm skeptical of "less than half" the performance, and wonder why that might be, but...
Again, it's rather uncommon that these inline messages are ever large. Bulk data (r/w >=4KB) is always carried by RDMA, and does not appear at all in these datagrams, for example.
The code currently has a single system-wide default, which is not tunable per connection and requires both sides of the connection to do so. It's not reasonable to depend on Windows, cifs.ko and ksmbd.ko to all somehow magically do the same thing. So the best default is the most conservative, least wasteful setting.
Tom.
Quoted 25 lines
Best,
Bernard.Quoted 22 lines
There might conceivably be a case for *smaller*, for example on IB when it's cranked down to the minimum (256B) MTU. But it will work with this default.
I'd say let's don't over-engineer it until we address the many other issues in this code. Merging the two smbdirect implementations is much more important than adding tweaky little knobs to both. MHO.
Tom.
Quoted 12 lines
Quoted 11 lines
Quoted 10 lines
Why does the specification describe setting it to 8192?
Quoted 7 lines
fs/ksmbd/transport_rdma.c +0
-1static int smb_direct_max_read_write_size =SMBD_DEFAULT_IOSIZE ; --2.34.1
RE: Re: [PATCH v2 4/6] Reduce server smbdirect max send/receive segment sizes
Quoted 128 lines
-----Original Message-----
From: Tom Talpey <[email protected]>
Sent: Wednesday, 28 September 2022 16:54
To: Bernard Metzler <[email protected]>; Namjae Jeon <[email protected]>
Cc: [email protected]; [email protected]; [email protected]; [email protected]; [email protected]
Subject: [EXTERNAL] Re: [PATCH v2 4/6] Reduce server smbdirect max send/receive segment sizesQuoted 102 lines · Bernard Metzler
Quoted 92 lines
-----Original Message-----
From: Tom Talpey <[email protected]>
Sent: Monday, 26 September 2022 19:25
To: Namjae Jeon <[email protected]>
Cc: [email protected]; [email protected]; [email protected]; Bernard Metzler <[email protected]>; [email protected]; [email protected]
Subject: [EXTERNAL] Re: [PATCH v2 4/6] Reduce server smbdirect max send/receive segment sizesQuoted 19 lines · Namjae Jeon
2022-09-26 0:41 GMT+09:00, Tom Talpey <[email protected]>:
Quoted 18 lines · Namjae Jeon
Quoted 17 lines
2022-09-24 6:53 GMT+09:00, Tom Talpey <[email protected]>:
Quoted 16 lines
Reduce ksmbd smbdirect max segment send and receive size to 1364 to match protocol norms. Larger buffers are unnecessary and add significant memory overhead.
Signed-off-by Tom Talpey <[email protected]>--- fs/ksmbd/transport_rdma.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)fs/ksmbd/transport_rdma.c +0
-0@@ -62,13 +62,13 @@ static int smb_direct_receive_credit_max = 255;static int smb_direct_send_credit_target =255 ;Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
fs/ksmbd/transport_rdma.c static int smb_direct_receive_credit_max = 255; · line 67
Quoted 5 lines
fs/ksmbd/transport_rdma.c +1
-1/* The maximum single message size can be sent to remote peer */ -static int smb_direct_max_send_size =8192 ; +static int smb_direct_max_send_size =1364 ;/* The maximum fragmented upper-layer payload receive size supported
Quoted 54 lines
Quoted 54 lines
Quoted 11 lines
fs/ksmbd/transport_rdma.c static int smb_direct_receive_credit_max = 255; · line 72
Quoted 6 lines
fs/ksmbd/transport_rdma.c +1
-1*/ static int smb_direct_max_fragmented_recv_size =1024 *1024 ;/* The maximum single-message size which can be received */ -static int smb_direct_max_receive_size =8192 ; +static int smb_direct_max_receive_size =1364 ;Can I know what value windows server set to ?
I can see the following settings for them in MS-SMBD.pdf Connection.MaxSendSize is set to 1364. Connection.MaxReceiveSize is set to 8192.
Glad you asked, it's an interesting situation IMO.
In MS-SMBD, the following are documented as behavior notes:
Client-side (active connect):
Connection.MaxSendSize is set to 1364.
Connection.MaxReceiveSize is set to 8192.Server-side (passive listen):
Connection.MaxSendSize is set to 1364.
Connection.MaxReceiveSize is set to 8192.However, these are only the initial values. During SMBD negotiation, the two sides adjust downward to the other's maximum. Therefore, Windows connecting to Windows will use 1364 on both sides.
In cifs and ksmbd, the choices were messier:
Client-side
smbdirect.c:int smbd_max_send_size = 1364; int smbd_max_receive_size = 8192;Server-side
transport_rdma.c:static int smb_direct_max_send_size = 8192; static int smb_direct_max_receive_size = 8192;Therefore, peers connecting to ksmbd would typically end up negotiating 1364 for send and 8192 for receive.
There is almost no good reason to use larger buffers. Because RDMA is highly efficient, and the smbdirect protocol trivially fragments longer messages, there is no significant performance penalty.
And, because not many SMB3 messages require 8192 bytes over smbdirect, it's a colossal waste of virtually contiguous kernel memory to allocate 8192 to all receives.
By setting all four to the practical reality of 1364, it's a consistent and efficient default, and aligns Linux smbdirect with Windows.
Quoted 9 lines
Quoted 3 lines
Thanks for your detailed explanation! Agree to set both to 1364 by default, Is there any usage to increase it? I wonder if users need any configuration parameters to adjust them.
In my opinion, probably not. I give some reasons why large fragments aren't always helpful just above. It's the same number of packets! Just a question of whether SMBDirect or Ethernet does the fragmentation, and the buffer management.
Quoted 5 lines
One simple reason for larger buffers I am aware of is running efficiently on software only RDMA providers like siw or rxe. For siw I'd guess we cut to less than half the performance with 1364 bytes buffers. But maybe that is no concern for the setups you have in mind.
I'm skeptical of "less than half" the performance, and wonder why that might be, but...
Again, it's rather uncommon that these inline messages are ever large. Bulk data (r/w >=4KB) is always carried by RDMA, and does not appear at all in these datagrams, for example.
Quoted 6 lines
The code currently has a single system-wide default, which is not tunable per connection and requires both sides of the connection to do so. It's not reasonable to depend on Windows, cifs.ko and ksmbd.ko to all somehow magically do the same thing. So the best default is the most conservative, least wasteful setting.
Oh, sorry, my bad. I was under the impression we talk about bulk data, if 8k buffers are the default. So I completely agree with your point.
Best,
Bernard.
Quoted 28 lines
Tom.
Quoted 25 lines
Best,
Bernard.Quoted 22 lines
There might conceivably be a case for *smaller*, for example on IB when it's cranked down to the minimum (256B) MTU. But it will work with this default.
I'd say let's don't over-engineer it until we address the many other issues in this code. Merging the two smbdirect implementations is much more important than adding tweaky little knobs to both. MHO.
Tom.
Quoted 12 lines
Quoted 11 lines
Quoted 10 lines
Why does the specification describe setting it to 8192?
Quoted 7 lines
fs/ksmbd/transport_rdma.c +0
-1static int smb_direct_max_read_write_size =SMBD_DEFAULT_IOSIZE ; --2.34.1
Re: [PATCH v2 4/6] Reduce server smbdirect max send/receive segment sizes
In reply to Tom Talpey2022-09-24 6:53 GMT+09:00, Tom Talpey <[email protected]>:
Quoted 5 lines
Reduce ksmbd smbdirect max segment send and receive size to 1364 to match protocol norms. Larger buffers are unnecessary and add significant memory overhead.
Signed-off-by Tom Talpey <[email protected]>
Thanks!
Tom Talpey
reviewerPATCH v2 5/6 Handle variable number of SGEs in client smbdirect send.
In reply to Tom TalpeyIf/when an outgoing request contains more scatter/gather segments than can be mapped in a single RDMA send work request, use smbdirect fragments to send it in multiple packets.
--- fs/cifs/smbdirect.c | 185 ++++++++++++++++++-------------------------- 1 file changed, 77 insertions(+), 108 deletions(-)
fs/cifs/smbdirect.c +77 -108
@@ -1984,10 +1984,11 @@ int smbd_send(struct TCP_Server_Info *server, int num_rqst, struct smb_rqst *rqst_array) { struct smbd_connection *info = server->smbd_conn; -struct kvec vec; +struct kvec vecs[SMBDIRECT_MAX_SEND_SGE -1 ];int nvecs;int size;unsigned int buflen, remaining_data_length; +unsigned int offset, remaining_vec_data_length;int start, i, j;int max_iov_size = info->max_send_size -sizeof (struct smbd_data_transfer );
@@ -1996,10 +1997,8 @@ int smbd_send(struct TCP_Server_Info *server,struct smb_rqst *rqst;int rqst_idx; -if (info->transport_status !=SMBD_CONNECTED ) { - rc = -EAGAIN ; - goto done; - } +if (info->transport_status !=SMBD_CONNECTED ) +return -EAGAIN ;/* * Add in the page array if there is one. The caller needs to set
@@ -2010,125 +2009,95 @@ int smbd_send(struct TCP_Server_Info *server,for (i =0 ; i < num_rqst; i++) remaining_data_length +=smb_rqst_len (server, &rqst_array[i]); -if (remaining_data_length > info->max_fragmented_send_size) { +if (unlikely (remaining_data_length > info->max_fragmented_send_size)) { +/* assertion: payload never exceeds negotiated maximum */ log_write (ERR ,"payload size %d > max size %d\n" , remaining_data_length, info->max_fragmented_send_size); - rc = -EINVAL ; - goto done; +return -EINVAL ; }log_write (INFO ,"num_rqst=%d total length=%u\n" , num_rqst, remaining_data_length); rqst_idx =0 ; -next_rqst: - rqst = &rqst_array[rqst_idx]; - iov = rqst->rq_iov; - -cifs_dbg (FYI ,"Sending smb (RDMA): idx=%d smb_len=%lu\n" , - rqst_idx,smb_rqst_len (server, rqst)); -for (i =0 ; i < rqst->rq_nvec; i++) -dump_smb (iov[i].iov_base, iov[i].iov_len); - - -log_write (INFO ,"rqst_idx=%d nvec=%d rqst->rq_npages=%d rq_pagesz=%d rq_tailsz=%d buflen=%lu\n" , - rqst_idx, rqst->rq_nvec, rqst->rq_npages, rqst->rq_pagesz, - rqst->rq_tailsz,smb_rqst_len (server, rqst)); - - start = i =0 ; - buflen =0 ; -while (true) { - buflen += iov[i].iov_len; -if (buflen > max_iov_size) { -if (i > start) { - remaining_data_length -= - (buflen-iov[i].iov_len); -log_write (INFO ,"sending iov[] from start=%d i=%d nvecs=%d remaining_data_length=%d\n" , - start, i, i - start, - remaining_data_length); - rc =smbd_post_send_data ( - info, &iov[start], i-start, - remaining_data_length); -if (rc) - goto done; - }else { -/* iov[start] is too big, break it */ - nvecs = (buflen+max_iov_size-1 )/max_iov_size; -log_write (INFO ,"iov[%d] iov_base=%p buflen=%d break to %d vectors\n" , - start, iov[start].iov_base, - buflen, nvecs); -for (j =0 ; j < nvecs; j++) { - vec.iov_base = - (char *)iov[start].iov_base + - j*max_iov_size; - vec.iov_len = max_iov_size; -if (j == nvecs-1 ) - vec.iov_len = - buflen - - max_iov_size*(nvecs-1 ); - remaining_data_length -= vec.iov_len; -log_write (INFO , -"sending vec j=%d iov_base=%p iov_len=%zu remaining_data_length=%d\n" , - j, vec.iov_base, vec.iov_len, - remaining_data_length); - rc =smbd_post_send_data ( - info, &vec,1 , - remaining_data_length); -if (rc) - goto done; +do { + rqst = &rqst_array[rqst_idx]; + iov = rqst->rq_iov; + +cifs_dbg (FYI ,"Sending smb (RDMA): idx=%d smb_len=%lu\n" , + rqst_idx,smb_rqst_len (server, rqst)); + remaining_vec_data_length =0 ; +for (i =0 ; i < rqst->rq_nvec; i++) { + remaining_vec_data_length += iov[i].iov_len; +dump_smb (iov[i].iov_base, iov[i].iov_len); + } + +log_write (INFO ,"rqst_idx=%d nvec=%d rqst->rq_npages=%d rq_pagesz=%d rq_tailsz=%d buflen=%lu\n" , + rqst_idx, rqst->rq_nvec, + rqst->rq_npages, rqst->rq_pagesz, + rqst->rq_tailsz,smb_rqst_len (server, rqst)); + + start =0 ; + offset =0 ; +do { + buflen =0 ; + i = start; + j =0 ; +while (i < rqst->rq_nvec && + j <SMBDIRECT_MAX_SEND_SGE -1 && + buflen < max_iov_size) { + + vecs[j].iov_base = iov[i].iov_base + offset; +if (buflen + iov[i].iov_len > max_iov_size) { + vecs[j].iov_len = + max_iov_size - iov[i].iov_len; + buflen = max_iov_size; + offset = vecs[j].iov_len; + }else { + vecs[j].iov_len = + iov[i].iov_len - offset; + buflen += vecs[j].iov_len; + offset =0 ; + ++i; } - i++; -if (i == rqst->rq_nvec) -break ; + ++j; } + + remaining_vec_data_length -= buflen; + remaining_data_length -= buflen; +log_write (INFO ,"sending %s iov[%d] from start=%d nvecs=%d remaining_data_length=%d\n" , + remaining_vec_data_length >0 ? +"partial" :"complete" , + rqst->rq_nvec, start, j, + remaining_data_length); + start = i; - buflen =0 ; - }else { - i++; -if (i == rqst->rq_nvec) { -/* send out all remaining vecs */ - remaining_data_length -= buflen; -log_write (INFO ,"sending iov[] from start=%d i=%d nvecs=%d remaining_data_length=%d\n" , - start, i, i - start, + rc =smbd_post_send_data (info, vecs, j, remaining_data_length); +if (rc) + goto done; + }while (remaining_vec_data_length >0 ); + +/* now sending pages if there are any */ +for (i =0 ; i < rqst->rq_npages; i++) { +rqst_page_get_length (rqst, i, &buflen, &offset); + nvecs = (buflen + max_iov_size -1 ) / max_iov_size; +log_write (INFO ,"sending pages buflen=%d nvecs=%d\n" , + buflen, nvecs); +for (j =0 ; j < nvecs; j++) { + size = min_t(unsigned int, max_iov_size, remaining_data_length); + remaining_data_length -= size; +log_write (INFO ,"sending pages i=%d offset=%d size=%d remaining_data_length=%d\n" , + i, j * max_iov_size + offset, size, remaining_data_length); - rc =smbd_post_send_data (info, &iov[start], - i-start, remaining_data_length); + rc =smbd_post_send_page ( + info, rqst->rq_pages[i], + j*max_iov_size + offset, + size, remaining_data_length);if (rc) goto done; -break ; } } -log_write (INFO ,"looping i=%d buflen=%d\n" , i, buflen); - } - -/* now sending pages if there are any */ -for (i =0 ; i < rqst->rq_npages; i++) { -unsigned int offset; - -rqst_page_get_length (rqst, i, &buflen, &offset); - nvecs = (buflen + max_iov_size -1 ) / max_iov_size; -log_write (INFO ,"sending pages buflen=%d nvecs=%d\n" , - buflen, nvecs); -for (j =0 ; j < nvecs; j++) { - size = max_iov_size; -if (j == nvecs-1 ) - size = buflen - j*max_iov_size; - remaining_data_length -= size; -log_write (INFO ,"sending pages i=%d offset=%d size=%d remaining_data_length=%d\n" , - i, j * max_iov_size + offset, size, - remaining_data_length); - rc =smbd_post_send_page ( - info, rqst->rq_pages[i], - j*max_iov_size + offset, - size, remaining_data_length); -if (rc) - goto done; - } - } - - rqst_idx++; -if (rqst_idx < num_rqst) - goto next_rqst; + }while (++rqst_idx < num_rqst); done:/*
Signature · 1 line
2.34.1
Tom Talpey
reviewerPATCH v2 6/6 Fix formatting of client smbdirect RDMA logging
In reply to Tom TalpeyMake the debug logging more consistent in formatting of addresses, lengths, and bitfields.
--- fs/cifs/smbdirect.c | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-)
fs/cifs/smbdirect.c +7 -7
@@ -270,7 +270,7 @@ static void send_done(struct ib_cq *cq, struct ib_wc *wc)struct smbd_request *request = container_of(wc->wr_cqe, struct smbd_request, cqe); -log_rdma_send (INFO ,"smbd_request %p completed wc->status=%d\n" , +log_rdma_send (INFO ,"smbd_request 0x%p completed wc->status=%d\n" , request, wc->status);if (wc->status !=IB_WC_SUCCESS || wc->opcode !=IB_WC_SEND ) {
@@ -448,7 +448,7 @@ static void recv_done(struct ib_cq *cq, struct ib_wc *wc)struct smbd_connection *info = response->info;int data_length =0 ; -log_rdma_recv (INFO ,"response=%p type=%d wc status=%d wc opcode %d byte_len=%d pkey_index=%x\n" , +log_rdma_recv (INFO ,"response=0x%p type=%d wc status=%d wc opcode %d byte_len=%d pkey_index=%u\n" , response, response->type, wc->status, wc->opcode, wc->byte_len, wc->pkey_index);
@@ -723,7 +723,7 @@ static int smbd_post_send_negotiate_req(struct smbd_connection *info) send_wr.opcode =IB_WR_SEND ; send_wr.send_flags =IB_SEND_SIGNALED ; -log_rdma_send (INFO ,"sge addr=%llx length=%x lkey=%x\n" , +log_rdma_send (INFO ,"sge addr=0x%llx length=%u lkey=0x%x\n" , request->sge[0 ].addr, request->sge[0 ].length, request->sge[0 ].lkey);
@@ -792,7 +792,7 @@ static int smbd_post_send(struct smbd_connection *info,for (i =0 ; i < request->num_sge; i++) {log_rdma_send (INFO , -"rdma_request sge[%d] addr=%llu length=%u\n" , +"rdma_request sge[%d] addr=0x%llx length=%u\n" , i, request->sge[i].addr, request->sge[i].length); ib_dma_sync_single_for_device( info->id->device,
@@ -1079,7 +1079,7 @@ static int smbd_negotiate(struct smbd_connection *info) response->type =SMBD_NEGOTIATE_RESP ; rc =smbd_post_recv (info, response); -log_rdma_event (INFO ,"smbd_post_recv rc=%d iov.addr=%llx iov.length=%x iov.lkey=%x\n" , +log_rdma_event (INFO ,"smbd_post_recv rc=%d iov.addr=0x%llx iov.length=%u iov.lkey=0x%x\n" , rc, response->sge.addr, response->sge.length, response->sge.lkey);if (rc)
@@ -1539,7 +1539,7 @@ static struct smbd_connection *_smbd_get_connection(if (smbd_send_credit_target > info->id->device->attrs.max_cqe || smbd_send_credit_target > info->id->device->attrs.max_qp_wr) { -log_rdma_event (ERR ,"consider lowering send_credit_target = %d. Possible CQE overrun, device reporting max_cpe %d max_qp_wr %d\n" , +log_rdma_event (ERR ,"consider lowering send_credit_target = %d. Possible CQE overrun, device reporting max_cqe %d max_qp_wr %d\n" , smbd_send_credit_target, info->id->device->attrs.max_cqe, info->id->device->attrs.max_qp_wr);
@@ -1548,7 +1548,7 @@ static struct smbd_connection *_smbd_get_connection(if (smbd_receive_credit_max > info->id->device->attrs.max_cqe || smbd_receive_credit_max > info->id->device->attrs.max_qp_wr) { -log_rdma_event (ERR ,"consider lowering receive_credit_max = %d. Possible CQE overrun, device reporting max_cpe %d max_qp_wr %d\n" , +log_rdma_event (ERR ,"consider lowering receive_credit_max = %d. Possible CQE overrun, device reporting max_cqe %d max_qp_wr %d\n" , smbd_receive_credit_max, info->id->device->attrs.max_cqe, info->id->device->attrs.max_qp_wr);
Signature · 1 line
2.34.1
Namjae Jeon
maintainer2022-09-24 6:53 GMT+09:00, Tom Talpey <[email protected]>:
Quoted 14 lines
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.
v2: correct an uninitialized value issue found by Coverity
Quoted 7 lines
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
You are missing adding prefix(cifs or ksmbd:) to each patch.
Quoted 10 lines
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
Tom Talpey
reviewerQuoted 15 lines · Namjae Jeon
2022-09-24 6:53 GMT+09:00, Tom Talpey <[email protected]>:
Quoted 14 lines
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.
v2: correct an uninitialized value issue found by Coverity
Quoted 8 lines
Quoted 7 lines
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 loggingYou are missing adding prefix(cifs or ksmbd:) to each patch.
Ok, sure I'll add those.
Tom.
Quoted 12 lines
Quoted 11 lines
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
merged patches 1, 3, 5, 6 of this series into cifs-2.6.git for-next (will let Namjae test/try the server patches, 2 and 4) pending additional testing.
Let me know if any Reviewed-by to add
Quoted 30 lines · Tom Talpey
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.
v2: correct an uninitialized value issue found by Coverity
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 loggingfs/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
Signature · 3 lines
Thanks, Steve
Tom Talpey
reviewerI need to add the "cifs" and "ksmbd" prefixes, and a couple of Acked-by's. I'm still pretty ill so not getting much done just now though. I'll try to get on it later today.
Quoted 39 lines · Steve French
merged patches 1, 3, 5, 6 of this series into cifs-2.6.git for-next (will let Namjae test/try the server patches, 2 and 4) pending additional testing.
Let me know if any Reviewed-by to add
Quoted 30 lines · Tom Talpey
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.
v2: correct an uninitialized value issue found by Coverity
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 loggingfs/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
I can add the Acked-bys if you send them to me (for the cifs.ko ones)
The client for server (cifs vs ksmbd prefix) in the title is more of an issue for email threads and patch review.
Quoted 45 lines · Tom Talpey
I need to add the "cifs" and "ksmbd" prefixes, and a couple of Acked-by's. I'm still pretty ill so not getting much done just now though. I'll try to get on it later today.
Quoted 39 lines · Steve French
merged patches 1, 3, 5, 6 of this series into cifs-2.6.git for-next (will let Namjae test/try the server patches, 2 and 4) pending additional testing.
Let me know if any Reviewed-by to add
Quoted 30 lines · Tom Talpey
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.
v2: correct an uninitialized value issue found by Coverity
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 loggingfs/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
Signature · 3 lines
Thanks, Steve
Tom Talpey
reviewerQuoted 1 line · Steve French
I can add the Acked-bys if you send them to me (for the cifs.ko ones)
That would be a big help!
Patch 1: Add "cifs:"
Patch 2: Add "ksmbd:" and Acked-by: Namjae Jeon <[email protected]> Patch 3: Add "cifs:"
Patch 4: Add "ksmbd:" and Acked-by: Namjae Jeon <[email protected]> Patch 5" Add "cifs:"
Patch 6: Add "cifs:"
No R-B's received, and no code changes.
Tom.
Quoted 53 lines
The client for server (cifs vs ksmbd prefix) in the title is more of an issue for email threads and patch review.
Quoted 45 lines · Tom Talpey
I need to add the "cifs" and "ksmbd" prefixes, and a couple of Acked-by's. I'm still pretty ill so not getting much done just now though. I'll try to get on it later today.
Quoted 39 lines · Steve French
merged patches 1, 3, 5, 6 of this series into cifs-2.6.git for-next (will let Namjae test/try the server patches, 2 and 4) pending additional testing.
Let me know if any Reviewed-by to add
Quoted 30 lines · Tom Talpey
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.
v2: correct an uninitialized value issue found by Coverity
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 loggingfs/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
Quoted 21 lines · Tom Talpey
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.
v2: correct an uninitialized value issue found by Coverity
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
Quoted 4 lines
fs/cifs/smbdirect.c | 227 ++++++++++++++++---------------------- fs/cifs/smbdirect.h | 14 ++- fs/ksmbd/transport_rdma.c | 6 +- 3 files changed, 109 insertions(+), 138 deletions(-)