Abhijit Bhopatkar wrote:
In my mind i find it fundamentally wrong to separate anon pages from
page cache. It should rather be lot more dependent on which task
accessed them last. Although it seems due to some twisted relationships
bet anon pages and interactive tasks separating them improves
Abhijit Bhopatkar wrote:
In my mind i find it fundamentally wrong to separate anon pages from
page cache. It should rather be lot more dependent on which task
accessed them last. Although it seems due to some twisted relationships
bet anon pages and interactive tasks separating them improves
> I just wanted to know weather its worth going forward or we have
> better reasons to discount any such direction?
The reason that the wrong pages get swapped out sometimes
could be due to a side effect of the way the swappiness
policy is implemented.
While the VM only reclaims page cache
Abhijit Bhopatkar wrote:
I just wanted to know weather its worth going forward or we have
better reasons to discount any such direction?
The reason that the wrong pages get swapped out sometimes
could be due to a side effect of the way the swappiness
policy is implemented.
While the VM only
अभिजित भोपटकर (Abhijit Bhopatkar) wrote:
The mm structures of interactive tasks are marked and
the pages belonging to them are never shifted to inactive
list in lru algorithm. Thus keeping interactive tasks in
memory as long as possible.
The interactivity is already determined by schedular so
we
अभिजित भोपटकर (Abhijit Bhopatkar) wrote:
The mm structures of interactive tasks are marked and
the pages belonging to them are never shifted to inactive
list in lru algorithm. Thus keeping interactive tasks in
memory as long as possible.
The interactivity is already determined by schedular so
we
The mm structures of interactive tasks are marked and
the pages belonging to them are never shifted to inactive
list in lru algorithm. Thus keeping interactive tasks in
memory as long as possible.
The interactivity is already determined by schedular so
we reuse that knowledge to mark the mm
The mm structures of interactive tasks are marked and
the pages belonging to them are never shifted to inactive
list in lru algorithm. Thus keeping interactive tasks in
memory as long as possible.
The interactivity is already determined by schedular so
we reuse that knowledge to mark the mm
अभिजित भोपटकर (Abhijit Bhopatkar) wrote:
The mm structures of interactive tasks are marked and
the pages belonging to them are never shifted to inactive
list in lru algorithm. Thus keeping interactive tasks in
memory as long as possible.
The interactivity is already determined by schedular so
we
अभिजित भोपटकर (Abhijit Bhopatkar) wrote:
The mm structures of interactive tasks are marked and
the pages belonging to them are never shifted to inactive
list in lru algorithm. Thus keeping interactive tasks in
memory as long as possible.
The interactivity is already determined by schedular so
we
Abhijit Bhopatkar wrote:
I just wanted to know weather its worth going forward or we have
better reasons to discount any such direction?
The reason that the wrong pages get swapped out sometimes
could be due to a side effect of the way the swappiness
policy is implemented.
While the VM only
I just wanted to know weather its worth going forward or we have
better reasons to discount any such direction?
The reason that the wrong pages get swapped out sometimes
could be due to a side effect of the way the swappiness
policy is implemented.
While the VM only reclaims page cache pages,
12 matches
Mail list logo
