Messages in this thread | | | Subject | Re: Why the DOS has many ntfs read and write driver,but the linux can't for a long time | From | Lee Revell <> | Date | Mon, 09 Jan 2006 11:04:06 -0500 |
| |
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/
| |