From mboxrd@z Thu Jan 1 00:00:00 1970 From: "David S. Ahern" Subject: Re: .img on nfs, relative on ram, consuming mass ram Date: Thu, 16 Sep 2010 08:49:50 -0600 Message-ID: <4C922E8E.2030907@cisco.com> References: <20100915113941.9536341d.f.tournier@iut.univ-paris8.fr> <4C91DEDD.9030508@amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: =?ISO-8859-1?Q?TOURNIER_Fr=E9d=E9ric?= , "kvm@vger.kernel.org" To: Andre Przywara Return-path: Received: from rtp-iport-1.cisco.com ([64.102.122.148]:26490 "EHLO rtp-iport-1.cisco.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755085Ab0IPOt7 (ORCPT ); Thu, 16 Sep 2010 10:49:59 -0400 In-Reply-To: <4C91DEDD.9030508@amd.com> Sender: kvm-owner@vger.kernel.org List-ID: On 09/16/10 03:09, Andre Przywara wrote: > Which is only natural, as tmpfs is promising to never swap. So it will pages in tmpfs can swap. That's difference between ramfs and tmpfs. From Documentation/filesystems/tmpfs.txt: "tmpfs puts everything into the kernel internal caches and grows and shrinks to accommodate the files it contains and is able to swap unneeded pages out to swap space." David