Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6768469
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 26, 20262026-05-26T15:04:44+00:00 2026-05-26T15:04:44+00:00

I’m trying to understand how exactly a cache miss occurs. So far this is

  • 0

I’m trying to understand how exactly a cache miss occurs. So far this is the way I understand it:
CPU requests for address x, searches its own (L1/L2) cache for it. If it is not there then it’s a cache miss.
Now what is missing here is how exactly does it find out that the information is not available in cache? What information do cache lines reserve? So far I know a cache line should contain this information:

Address of the information, Data within that address.  

Having this information CPU can find out whether an address is available in its cache or not. The problem arises when, it has an invalid copy of data. So my question would be:
How does the processor find out if some data is valid or invalid?
Are there flags stored in each cache line? Does it ask the protocol for this information? If so, where are protocol’s information kept(Cache/Memory/Elsewhere)?
I’m still searching, but I’d appreciate any resources on this.

–EDIT
Similar question asked here, yet no answer. There doesn’t seem to be any detailed information of MESI protocol. Any help is appreciated.

–EDIT2
I found more info in MESI CMP Directory. It states that “L2 cache controller on-chip directory is co-located with the corresponding cache blocks in L2 Cache”, but nothing about where L1 cache controller information resides.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-26T15:04:44+00:00Added an answer on May 26, 2026 at 3:04 pm

    The cache line (L1 or L2) contains the following information:

    dirty_bit | many_memory_word
    

    When the dirty bit contains 1 that means the line cache is not similar to the correspondent in the RAM. When it contains 0 that means the line cache contains the exact copy of the memory line actually in the RAM.

    When the CPU request an address in the RAM, a translation is made using the MTL to have a correspondent line cache address which is supposed to contain the information.

    If there is no address found, that means the information is not on the cache line and then a cache miss happens. If an address on the cache is found, then if the dirty bit of the line requested in the cache is set to 1, a cache miss will happen, and the information actually in the line cache will be written back in memory. The address of the line in the cache makes the CPU know which address corresponds in the real memory RAM.

    So when the CPU requesst an information from memory, this information (and more) are put on the line cache, and the dirty bit is set to 0 that means that the cache line represents the exact copy of memory line in the RAM.

    Then, when writing operations occur in the line cache, the CPU sets the dirty bit to 1 that means the line does no longer represent the copy actually present in the RAM. So if a reading operation occurs on an address in the cache whose dirty bit is set to 1, a cache miss happens.

    Reference: have a look here for more.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I am trying to understand how to use SyndicationItem to display feed which is
I have a string like this: La Torre Eiffel paragonata all’Everest What PHP function
I'm parsing an RSS feed that has an ’ in it. SimpleXML turns this
Basically, what I'm trying to create is a page of div tags, each has
link Im having trouble converting the html entites into html characters, (&# 8217;) i
For some reason, after submitting a string like this Jack’s Spindle from a text
this is what i have right now Drawing an RSS feed into the php,
I am trying to render a haml file in a javascript response like so:
I have this code to decode numeric html entities to the UTF8 equivalent character.
I have this code: - (void)parser:(NSXMLParser *)parser foundCDATA:(NSData *)CDATABlock { NSString *someString = [[NSString

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.