--On Sunday, November 16, 2003 19:39 -0500 Rob Murawski <[EMAIL PROTECTED]> wrote:
Since the memory-mapped file is addressed as if it were memory, it should be fairly easy to change the startup code to malloc an appropriate amount of memory instead of creating the memory-mapped file. I would presume no one has had the need to do this before.
-Rob
----- Original Message ----- From: Christopher D. Clausen To: [EMAIL PROTECTED] Sent: Sunday, November 16, 2003 7:31 PM Subject: Re: [OpenAFS] memcache option for Windows client
Rob Murawski <[EMAIL PROTECTED]> wrote:An in-memory cache option doesn't make sense for the Windows client. It uses a memory mapped file for the cache. This means that, if sufficient memory exists, it is in memory. It basically works like virtual memory where it will be mapped back to the disk when needed, but is addressable like memory.
Do you have a need that the cache ONLY be in memory?
Actually, yes.
I have some clients with largish amounts of RAM, low disk space, and slow disks. It would be nice to avoid disk writes, as it significantly reduces performance. And the cache size would not be dependant on the amount of free disk space on the machine, but only the RAM.
Perhaps it might be time to buy some larger, faster disks.
I was also attempting to create a disk-less Windows client using Windows XP embedded, where disk access would complicate matters (although I have not gotten far yet.)
<<CDC Christopher D. Clausen [EMAIL PROTECTED] SysAdmin
_______________________________________________ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
-- Undocumented Features quote of the moment... "It's not the one bullet with your name on it that you have to worry about; it's the twenty thousand-odd rounds labeled `occupant.'" --Murphy's Laws of Combat
_______________________________________________ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
