From: Evgeniy Polyakov Subject: Re: [patch 18/21] Filesystem: Socket inode defragmentation Date: Tue, 13 May 2008 17:28:12 +0400 Message-ID: <20080513132810.GA7152@2ka.mipt.ru> References: <20080510030831.796641881@sgi.com> <20080510030918.882272887@sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, linux-fsdevel@vger.kernel.org, Mel Gorman , andi@firstfloor.org, Rik van Riel , Pekka Enberg , mpm@selenic.com To: Christoph Lameter Return-path: Content-Disposition: inline In-Reply-To: <20080510030918.882272887@sgi.com> Sender: netdev-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Hi Christoph. On Fri, May 09, 2008 at 08:08:49PM -0700, Christoph Lameter (clameter@sgi.com) wrote: > Support inode defragmentation for sockets 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? -- Evgeniy Polyakov