<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/dc63dadf34a849959a4ff6e1c3c3133f&quot; frameborder=&quot;0&quot; width=&quot;1672&quot; height=&quot;1254&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1254</height><width>1672</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1254</thumbnail_height><thumbnail_width>1672</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/dc63dadf34a849959a4ff6e1c3c3133f-86b42c9c3b8d9054.gif</thumbnail_url><duration>1634.429</duration><title>Understanding XV6 Copy-On-Write </title><description>In this video, I explain the concept of copy-on-write (COW) in memory management, particularly how it relates to parent and child processes. I discuss the allocation of physical memory and the handling of read-only and writable pages during the forking process. It&apos;s crucial to understand how we can save memory by sharing pages and only allocating new ones when necessary. I encourage you to review the code I mentioned to see how these mechanisms are implemented. Please let me know if you have any questions or need further clarification.

@jerryq0101 on X</description></oembed>