From: Oliver Neukum <oliver@neukum.org>
To: Robert Hancock <hancockr@shaw.ca>
Subject: Re: Why the DOS has many ntfs read and write driver,but the linux can't for a long time
Date: Mon, 9 Jan 2006 15:28:18 +0100
User-Agent: KMail/1.8
Cc: linux-kernel <linux-kernel@vger.kernel.org>
References: <5t06S-7nB-15@gated-at.bofh.it> <5t5JU-7Sn-11@gated-at.bofh.it> <43C270B2.4050305@shaw.ca>
In-Reply-To: <43C270B2.4050305@shaw.ca>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200601091528.19285.oliver@neukum.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 946
Lines: 19

Am Montag, 9. Januar 2006 15:18 schrieb Robert Hancock:
> Yaroslav Rastrigin wrote:
> > Well, I could find more or less reasonable explanation of this behaviour - different VM policies of two OSes and 
> > strangely strong and persistent belief "Free RAM is a wasted RAM" among kernel devs. Free RAM is not a wasted RAM, its a memory waiting to be used ! 
> > Whenever it is needed by apps I'm launching or working with. 
> 
> There is no different VM policy here, Windows behaves quite similarly. 
> It does not leave memory around unused, it uses it for disk cache.

That doesn't mean that the rate of eviction is the same.
Is it possible that read-ahead is not aggressive enough?

	Regards
		Oliver
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/