Date: Mon, 1 Feb 2010 11:53:52 -0600 (CST)
From: Christoph Lameter <cl@linux-foundation.org>
To: Rik van Riel <riel@redhat.com>
cc: Andi Kleen <andi@firstfloor.org>, Dave Chinner <david@fromorbit.com>,
       Pekka Enberg <penberg@cs.helsinki.fi>, akpm@linux-foundation.org,
       Miklos Szeredi <miklos@szeredi.hu>,
       Nick Piggin <nickpiggin@yahoo.com.au>, Hugh Dickins <hugh@veritas.com>,
       linux-kernel@vger.kernel.org, viro@ZenIV.linux.org.uk
Subject: Re: Slab Fragmentation Reduction V15
In-Reply-To: <4B6447EC.7030702@redhat.com>
Message-ID: <alpine.DEB.2.00.1002011152510.30861@router.home>
References: <20100129204931.789743493@quilx.com> <20100130104812.GE29555@one.firstfloor.org> <4B6447EC.7030702@redhat.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1091
Lines: 32

On Sat, 30 Jan 2010, Rik van Riel wrote:

> On 01/30/2010 05:48 AM, Andi Kleen wrote:
> > On Fri, Jan 29, 2010 at 02:49:31PM -0600, Christoph Lameter wrote:
>
> > > 	1. Establish a reference to an dentry/inode so that it is pinned.
> > >             Hopefully in a way that is not too expensive (i.e. no
> > > superblock
> > >             lock)
> > >
> > > 	2. A means to free a dentry/inode objects from the VM reclaim context.
> >
> >
> > Al, do you have a suggestions on a good way to do that?
>
> You cannot free inode objects for files that are open, mmapped, etc.

Of course. Those objects need to prevent reclaim attempts.

> > I guess the problem could be simplified by ignoring dentries in "unusual"
> > states?
>
> You mean dentries that are in use? :)

The existing patch already tried to discern that and avoid the reclaim of
these.

--
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/