git.samba.org / metze / samba / wip.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 46eacae) | patch
s3:torture/*: use CLI_BUFFER_SIZE instead of cli->max_xmit
authorStefan Metzmacher <metze@samba.org>
Tue, 2 Aug 2011 20:59:54 +0000 (22:59 +0200)
committerStefan Metzmacher <metze@samba.org>
Tue, 9 Aug 2011 13:30:04 +0000 (15:30 +0200)
commit70c2bbecde434264e0b54279f13159e9991efade
treef01a9018a7114d51192fc327d84d06e419291f7btree
parent46eacae8b516c0a2b9c372af0baadc436f64d957commit | diff
s3:torture/*: use CLI_BUFFER_SIZE instead of cli->max_xmit

The max_data parameter of trans2/nttrans calls are not bound
to cli->max_xmit. Even with cli->max_xmit, which means the max
size of the whole SMB pdu, we would get fragmented trans2/nttrans
replies. That's why we can also use our maximum, which is CLI_BUFFER_SIZE.

metze
source3/torture/nbench.c diff | blob | history
source3/torture/scanner.c diff | blob | history
Work in progress branches