top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Detailed info about snooping used in cache Cache Coherency ?

+3 votes
330 views

Any link or detailed info available to understand snooping ?

posted Apr 23, 2015 by Sachidananda Sahu

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

+2 votes

Snooping is the process where the individual caches monitor address lines for accesses to memory locations that they have cached. When a write operation is observed to a location that a cache has a copy of, the cache controller invalidates its own copy of the snooped memory location.

Not sure the about the detail requirement of the problem but you may look into the following link and comment back if there is any specific need.
https://numascale.com/snooping.html

answer Apr 23, 2015 by Salil Agrawal
Similar Questions
+1 vote
Few questions about Cache memory

I have few questions about Cache Memory

In my system "free -h" command gave me below output,

      total        used        free      shared  buff/cache   available
Mem:   7.6G        2.1G        1.5G         46M        4.0G        4.8G
Swap:  1.6G         28M        1.6G

1. Why "Cache Memory" is required inside the main memory?

As far as i know "Cache Memory" is different than the main memory(RAM), It is very costly and it is very faster, Please Correct me if i am wrong.

2. Before 1 hour this cache memory was 3 GB and then it is increased by 1 GB?

Please note that I din't start/run any new processes

3. Till what limit i can start new processes/application?

I mean as per free -h command output, 

free memory = 1.5 GB, Cache memory = 4 GB and Swap memory = 1.6 GB

can i start new application up to (1.5 + 1.6) GB or (1.5 + 1.6 + 4) GB`?

4. Can i set/configure this cache memory value?

If yes, then how to?

+2 votes
OS: How I can see number of threads belong one process running in machine ?

Which option is used in "ps" command to get the details on running threads associated to a process ?

+3 votes
Open system call in linux

I noticed that there are two prototypes for open system call in linux,

int open(const char *pathname, int flags);
int open(const char *pathname, int flags, mode_t mode);

I would like to know how the C compiler can differentiate b/w both calls, given C compiler doesn't support function overloading?

...