login
Login / Register
Header Space

 
 

Home » Mailing list archives » linux-kernel » 2008 » May » 13

Re: [patch 18/21] Filesystem: Socket inode defragmentation

Score:
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
[view in full thread]
From: Evgeniy Polyakov <johnpol@...>
To: Christoph Lameter <clameter@...>
Cc: <akpm@...>, <linux-kernel@...>, <netdev@...>, <linux-fsdevel@...>, Mel Gorman <mel@...>, <andi@...>, Rik van Riel <riel@...>, Pekka Enberg <penberg@...>, <mpm@...>
Subject: Re: [patch 18/21] Filesystem: Socket inode defragmentation
Date: Tuesday, May 13, 2008 - 9:28 am

Hi Christoph.

On Fri, May 09, 2008 at 08:08:49PM -0700, Christoph Lameter (clameter@sgi.com) 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?

-- 
	Evgeniy Polyakov
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
Messages in current thread:
[patch 18/21] Filesystem: Socket inode defragmentation, Christoph Lameter, (Fri May 9, 11:08 pm)
Re: [patch 18/21] Filesystem: Socket inode defragmentation, Evgeniy Polyakov, (Tue May 13, 9:28 am)
Re: [patch 18/21] Filesystem: Socket inode defragmentation, Christoph Lameter, (Thu May 15, 1:40 pm)
Re: [patch 18/21] Filesystem: Socket inode defragmentation, Evgeniy Polyakov, (Thu May 15, 2:23 pm)

Mail archive search
Enter your search terms.
Optionally limit your search to a specific mailing list.
advanced
Colocation donated by:
Who's online
There are currently 3 users and 729 guests online.

Online users

Syndicate
Syndicate content
© 2007 KernelTrap.  |  Powered by Drupal.  |  Legal statement.
speck-geostationary