{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiagrum53js4hku62sv7ddnzpu4xph2zzj45333ucwyb6h5mklygxq",
    "uri": "at://did:plc:b3tz6srl4ochk2wxn6dv6xpy/app.bsky.feed.post/3mhw6mg674i52"
  },
  "path": "/Articles/1064090/",
  "publishedAt": "2026-03-25T14:32:30.000Z",
  "site": "https://lwn.net",
  "textContent": "The kernel's direct map provides code running in kernel mode with direct\naccess to all physical memory installed in the system — on 64-bit systems,\nat least.  It obviously makes life easier for kernel developers, but the\ndirect map also brings some problems of its own, most of which are\nsecurity-related.  Interest in removing at least some pages from the direct\nmap has been simmering for years; a couple of patch sets under \ndiscussion show some use cases for memory that has been removed from the\ndirect map, and how such memory might be efficiently managed.",
  "title": "[$] More efficient removal of pages from the direct map"
}