lkml.org 
[lkml]   [2006]   [Jan]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: Why the DOS has many ntfs read and write driver,but the linux can't for a long time
From
Date
On Mon, 2006-01-09 at 17:02 +0100, Oliver Neukum wrote:
> Am Montag, 9. Januar 2006 16:15 schrieb Lee Revell:
> > 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?
>
> Quicker application startup.

Why do you look to the kernel first? The obvious explanation is that
Linux desktop apps are more bloated than their Windows counterparts.

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/

\
 
 \ /
  Last update: 2006-01-09 17:06    [W:2.050 / U:0.084 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site