On Wed, Feb 20, 2013 at 10:01 PM, Soham Chakraborty
sohamwonderpik...@gmail.com wrote:
The question is salivating and simple. When we have free and lotsa cached
memory in a system (irrespective of distro and kernel), why would some
process end up in swap space, I understand the overcommit mode
On Thu, Feb 21, 2013 at 12:19 AM, Soham Chakraborty
sohamwonderpik...@gmail.com wrote:
On Thu, Feb 21, 2013 at 10:45 AM, Mandeep Sandhu
mandeepsandhu@gmail.com wrote:
I know the pages are kept on disk initially and then swapped in as
needed/referenced. Thus if there are code pages
Hi all,
I posted this question in linux-mm list as well but it didn't spawn much
interest. So, I am putting the same question here also. Would love if
someone can put some traction.
The question is salivating and simple. When we have free and lotsa cached
memory in a system (irrespective of
Hi!
On 20:31 Wed 20 Feb , Soham Chakraborty wrote:
Hi all,
I posted this question in linux-mm list as well but it didn't spawn much
interest. So, I am putting the same question here also. Would love if
someone can put some traction.
The question is salivating and simple. When we have
Soham Chakraborty sohamwonderpik...@gmail.com wrote:
Hi all,
I posted this question in linux-mm list as well but it didn't spawn
much
interest. So, I am putting the same question here also. Would love if
someone can put some traction.
The question is salivating and simple. When we have free
I know the pages are kept on disk initially and then swapped in as
needed/referenced. Thus if there are code pages where none of the code in
the page has been executed since starting the app, then that page will remain
on disk until the application logic eventually invokes it. At that
On Thu, Feb 21, 2013 at 10:45 AM, Mandeep Sandhu
mandeepsandhu@gmail.com wrote:
I know the pages are kept on disk initially and then swapped in as
needed/referenced. Thus if there are code pages where none of the code in
the page has been executed since starting the app, then that page
