[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0805151039060.18708@schroedinger.engr.sgi.com>
Date: Thu, 15 May 2008 10:40:11 -0700 (PDT)
From: Christoph Lameter <clameter@....com>
To: Evgeniy Polyakov <johnpol@....mipt.ru>
cc: akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, linux-fsdevel@...r.kernel.org,
Mel Gorman <mel@...net.ie>, andi@...stfloor.org,
Rik van Riel <riel@...hat.com>,
Pekka Enberg <penberg@...helsinki.fi>, mpm@...enic.com
Subject: Re: [patch 18/21] Filesystem: Socket inode defragmentation
On Tue, 13 May 2008, Evgeniy Polyakov wrote:
> Out of curiosity, how can you drop socket inode, since it is always
> attached to socket which is removed automatically when connection is
> closed. Any force of dropping socket inode can only result in connection
> drop, i.e. there are no inodes, which are placed in cache and are not
> yet freed, if there are no attached sockets.
>
> So question is how does it work for sockets?
All inodes are inactivated and put on a lru before they are freed. Those
could be reclaimed by inode defrag. Socket inode defrag is not that
important. Just shows that this can be applied in a general way.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists