git.samba.org / metze / samba / wip.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: bd64aba) | 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, 2 Aug 2011 21:15:14 +0000 (23:15 +0200)
commitf69dd6c9d8b0d48f7f0459f9272feebc5e40beb7
tree1d11871d0bd592d747b6fd452e92215a3e3add60tree
parentbd64aba490714e57e00e768dd2c0a47cf94549f3commit | 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