Re: [patch 18/21] Filesystem: Socket inode defragmentation
- Date: Thu, 15 May 2008 10:40:11 -0700 (PDT)
- From: Christoph Lameter <clameter@xxxxxxx>
- 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 linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/