mirror of
https://git.openafs.org/openafs.git
synced 2025-01-19 23:40:13 +00:00
Use bigger I/O sizes for the memcache
There doesn't seem to be a need to limit the rx message size when using rx_WritevAlloc. If there arent enough rx buffers to hold the entire message at once, it will simply return less space. Change-Id: Ic1e99432c8e4d21c71f831b8d6aeea9f12b1c99c Reviewed-on: http://gerrit.openafs.org/2943 Tested-by: BuildBot <buildbot@rampaginggeek.com> Reviewed-by: Derrick Brashear <shadow@dementia.org> Tested-by: Derrick Brashear <shadow@dementia.org>
This commit is contained in:
parent
5142f16bd3
commit
6880d4a3a2
@ -93,9 +93,8 @@ rxfs_storeMemPrepare(void *r, afs_uint32 size, afs_uint32 *tlen)
|
||||
afs_int32 code;
|
||||
struct rxfs_storeVariables *v = (struct rxfs_storeVariables *) r;
|
||||
|
||||
*tlen = (size > AFS_LRALLOCSIZ ? AFS_LRALLOCSIZ : size);
|
||||
RX_AFS_GUNLOCK();
|
||||
code = rx_WritevAlloc(v->call, v->tiov, &v->tnio, RX_MAXIOVECS, *tlen);
|
||||
code = rx_WritevAlloc(v->call, v->tiov, &v->tnio, RX_MAXIOVECS, size);
|
||||
RX_AFS_GLOCK();
|
||||
if (code <= 0) {
|
||||
code = rx_Error(v->call);
|
||||
|
Loading…
Reference in New Issue
Block a user