<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Tlb on DAMON Project Website</title>
    <link>https://damonitor.github.io/tags/tlb/</link>
    <description>Recent content in Tlb on DAMON Project Website</description>
    <image>
      <title>DAMON Project Website</title>
      <url>https://damonitor.github.io/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</url>
      <link>https://damonitor.github.io/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</link>
    </image>
    <generator>Hugo -- 0.131.0</generator>
    <language>en</language>
    <lastBuildDate>Tue, 09 Jun 2026 00:00:00 +0800</lastBuildDate>
    <atom:link href="https://damonitor.github.io/tags/tlb/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>DAMON TLB Flush Policy</title>
      <link>https://damonitor.github.io/posts/tlb_flush_policy/</link>
      <pubDate>Tue, 09 Jun 2026 00:00:00 +0800</pubDate>
      <guid>https://damonitor.github.io/posts/tlb_flush_policy/</guid>
      <description>Authors: Kunwu Chan &amp;lt;kunwu.chan@gmail.com&amp;gt;, Wang Lian &amp;lt;lianux.mm@gmail.com&amp;gt;
Overview DAMON monitors data access by sampling PTE (Page Table Entry) Accessed bits. It clears the Accessed bit but does not flush the TLB (Translation Lookaside Buffer). This is an intentional design choice.
Questions about this behavior come up repeatedly, both on the mailing list and in private inquiries. This document describes the reasoning, the trade-offs, and recommendations for users and testers.
Background DAMON&amp;rsquo;s access check works as follows:</description>
    </item>
  </channel>
</rss>
