On Tue, Aug 20, 2013 at 01:59:24PM -0700, Andrew Morton wrote:
> On Sat, 17 Aug 2013 15:31:23 -0400 Johannes Weiner wrote:
>
> > Previously, page cache radix tree nodes were freed after reclaim
> > emptied out their page pointers. But now reclaim stores shadow
> > entries in their place, which
On Tue, Aug 20, 2013 at 01:59:24PM -0700, Andrew Morton wrote:
On Sat, 17 Aug 2013 15:31:23 -0400 Johannes Weiner han...@cmpxchg.org wrote:
Previously, page cache radix tree nodes were freed after reclaim
emptied out their page pointers. But now reclaim stores shadow
entries in their
On Sat, 17 Aug 2013 15:31:23 -0400 Johannes Weiner wrote:
> Previously, page cache radix tree nodes were freed after reclaim
> emptied out their page pointers. But now reclaim stores shadow
> entries in their place, which are only reclaimed when the inodes
> themselves are reclaimed. This is
On Sat, 17 Aug 2013 15:31:23 -0400 Johannes Weiner han...@cmpxchg.org wrote:
Previously, page cache radix tree nodes were freed after reclaim
emptied out their page pointers. But now reclaim stores shadow
entries in their place, which are only reclaimed when the inodes
themselves are
Previously, page cache radix tree nodes were freed after reclaim
emptied out their page pointers. But now reclaim stores shadow
entries in their place, which are only reclaimed when the inodes
themselves are reclaimed. This is problematic for bigger files that
are still in use after they have a
Previously, page cache radix tree nodes were freed after reclaim
emptied out their page pointers. But now reclaim stores shadow
entries in their place, which are only reclaimed when the inodes
themselves are reclaimed. This is problematic for bigger files that
are still in use after they have a
Hey Andi!
On Mon, Aug 12, 2013 at 01:56:31AM +0200, Andi Kleen wrote:
>
> I really like the idea of using the spare slots in the radix tree
> for something useful. It's amazing we haven't used that before.
>
> I wonder if with some clever encoding even more information could be fit?
What do
Hey Andi!
On Mon, Aug 12, 2013 at 01:56:31AM +0200, Andi Kleen wrote:
I really like the idea of using the spare slots in the radix tree
for something useful. It's amazing we haven't used that before.
I wonder if with some clever encoding even more information could be fit?
What do you
I really like the idea of using the spare slots in the radix tree
for something useful. It's amazing we haven't used that before.
I wonder if with some clever encoding even more information could be fit?
e.g. I assume you don't really need all bits of the refault distance,
just a good enough
I really like the idea of using the spare slots in the radix tree
for something useful. It's amazing we haven't used that before.
I wonder if with some clever encoding even more information could be fit?
e.g. I assume you don't really need all bits of the refault distance,
just a good enough
Previously, page cache radix tree nodes were freed after reclaim
emptied out their page pointers. But now reclaim stores shadow
entries in their place, which are only reclaimed when the inodes
themselves are reclaimed. This is problematic for bigger files that
are still in use after they have a
Previously, page cache radix tree nodes were freed after reclaim
emptied out their page pointers. But now reclaim stores shadow
entries in their place, which are only reclaimed when the inodes
themselves are reclaimed. This is problematic for bigger files that
are still in use after they have a
12 matches
Mail list logo
