Writing /fs1/eecg/moshovos/a/a3/moshovos/public_www/filter/data/cache/d/d7afb0852257f93c8226f5cc52cd05d0.i failed
Unable to save cache file. Hint: disk full; file permissions; safe_mode setting.
Writing /fs1/eecg/moshovos/a/a3/moshovos/public_www/filter/data/cache/d/d7afb0852257f93c8226f5cc52cd05d0.i failed
Unable to save cache file. Hint: disk full; file permissions; safe_mode setting.
Writing /fs1/eecg/moshovos/a/a3/moshovos/public_www/filter/data/cache/d/d7afb0852257f93c8226f5cc52cd05d0.xhtml failed

As an alternative to directory protocols, snoop-based coherence protocols require less storage space and offer the potential for higher performance. Instead of relying on a single structure to track the location of all cached copies of a block, snoop protocols broadcast \emph{snoop} messages to all caches to locate the copies on-demand. When a cache received one of these snoop messages, it performs a tag array lookup to determine whether it has a copy of the requested block, and sends a reply accordingly. Since broadcasts can be sent directly from the requesting node without first sending a message to a directory, the latency for finding an up-to-date copy of the requested block can be lower than for directory protocols resulting in better overall performance.

 
snoop_intro.txt · Last modified: 2010/10/12 15:29 by andreas
 
Except where otherwise noted, content on this wiki is licensed under the following license:CC Attribution-Noncommercial-Share Alike 3.0 Unported
Recent changes RSS feed Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki