Re: Why the DOS has many ntfs read and write driver,but the linux can't for a long time

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.

--
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from [email protected]
Home Page: http://www.roberthancock.com/

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

---

• Follow-Ups:
  • Re: Why the DOS has many ntfs read and write driver,but the linux can't for a long time
    • From: Oliver Neukum <[email protected]>

• Prev by Date: Re: [PATCH 2/5] rcu: don't check ->donelist in __rcu_pending()
• Next by Date: Re: 2.6.15 cfq oops
• Previous by thread: Re: Why the DOS has many ntfs read and write driver,but the linux can't for a long time
• Next by thread: Re: Why the DOS has many ntfs read and write driver,but the linux can't for a long time
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]