Date: Tue, 06 Jun 1995 11:47:01 -0700 From: David Greenman <davidg@Root.COM> To: Stephen Hocking <sysseh@devetir.qld.gov.au> Cc: bugs@FreeBSD.org Subject: Re: 2.0.5-A: Very disheartening? Message-ID: <199506061848.LAA00541@corbin.Root.COM> In-Reply-To: Your message of "Tue, 06 Jun 95 11:04:31 GMT." <199506061104.LAA15596@netfl15a.devetir.qld.gov.au>
next in thread | previous in thread | raw e-mail | index | archive | help
> Might this not have something to do with unzipping something >executable into memory and then failing to invalidate the cache entries for >the memory you've just unzipped into? It sounds like a failure mode that >you'd see with machines that have split I/D caches. I know it's easy to yell >suggestions from the sidelines, but wouldn't it be a good idea to invalidate >the cache after the image has been unzipped into memory? No. If you don't have cache coherency for things the *CPU* writes to memory, you may as well pack up your marbles and go home. The problem isn't likely caused by any sort of cache problem (even though it is apparantly effected by disabling the cache). -DG
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199506061848.LAA00541>