Subject: Re: Why the DOS has many ntfs read and write driver,but the linux
	can't for a long time
From: Lee Revell <rlrevell@joe-job.com>
To: Oliver Neukum <oliver@neukum.org>
Cc: Robert Hancock <hancockr@shaw.ca>,
       linux-kernel <linux-kernel@vger.kernel.org>
In-Reply-To: <200601091528.19285.oliver@neukum.org>
References: <5t06S-7nB-15@gated-at.bofh.it> <5t5JU-7Sn-11@gated-at.bofh.it>
	 <43C270B2.4050305@shaw.ca>  <200601091528.19285.oliver@neukum.org>
Content-Type: text/plain
Date: Mon, 09 Jan 2006 10:15:47 -0500
Message-Id: <1136819748.9957.12.camel@mindpipe>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1081
Lines: 22

On Mon, 2006-01-09 at 15:28 +0100, Oliver Neukum wrote:
> 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?

Enough for what?  What is the exact problem you are trying to solve?

Lee

-
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/