<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Swap on Saleem Ansari</title>
    <link>/tags/swap/</link>
    <description>Recent content in Swap on Saleem Ansari</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>(c) 2024 Saleem Ansari</copyright>
    <lastBuildDate>Mon, 14 Dec 2009 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/swap/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How does live linux disk work without any swap for applications bigger than available RAM?</title>
      <link>/2009/12/14/how-does-live-linux-disk-work-without-any-swap-for-applications-bigger-than-available-ram/</link>
      <pubDate>Mon, 14 Dec 2009 00:00:00 +0000</pubDate>
      <guid>/2009/12/14/how-does-live-linux-disk-work-without-any-swap-for-applications-bigger-than-available-ram/</guid>
      <description>How does live linux disk work without any swap for applications bigger than available RAM? This question has occurred to me a lot of times. In the normal scenario I configure enough swap space on the harddis for my GNU/Linux installation. It looks clear that whenever a new request for memory is made by an application, the Linux kernel (OS) gives that request by swapping out a page into swap space ( when there wasn&amp;rsquo;t enought space available in RAM).</description>
    </item>
  </channel>
</rss>
