From 6880d4a3a227f6c05332ef799123e0a05b190aa9 Mon Sep 17 00:00:00 2001 From: "Chas Williams (CONTRACTOR)" Date: Thu, 7 Oct 2010 11:05:50 -0400 Subject: [PATCH] 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 Reviewed-by: Derrick Brashear Tested-by: Derrick Brashear --- src/afs/afs_fetchstore.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/afs/afs_fetchstore.c b/src/afs/afs_fetchstore.c index 5dcbc1a8bf..f34c96eb77 100644 --- a/src/afs/afs_fetchstore.c +++ b/src/afs/afs_fetchstore.c @@ -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);