Okay, after a quick google-ing I think I understand the differences between kmalloc() and vmalloc(). I'm guessing, though, that this cache is different than the one I set to 500MB while installing the openafs client.
I'm just running bog-standard fairly-modern desktops and laptops here... what cache settings will likely yield the best performance? Thanks, Karl -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chas Williams (CONTRACTOR) Sent: Saturday, November 08, 2008 7:21 AM To: Karl M. Davis Cc: [email protected] Subject: Re: [OpenAFS] Weird conflict between openafs kernel module and nvidia driver on Ubuntu In message <[EMAIL PROTECTED]>,"Karl M. Davis" writes: > As part of my standard setup, I've been editing /etc/openafs/afs.conf: > << > ... > #OPTIONS=AUTOMATIC > OPTIONS="-chunksize 20 -memcache -blocks 65536" setting chunksize to 20 (1MB) and using memcache will cause the allocator to use vmalloc() instead of kmalloc(). vm space is a bit limited on some systems. using the memcache i wouldnt consider a chunksize over 15. since your cache is generally smaller with memcache bigger chunksizes tends to force the number of files you can hold to a smaller number. _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
