maybe. every socket has an inode and probably a dentry associated with
it, true?
in that case, every filesystem iget operation has to wade through 100K+
inodes to find an inode (imagine the length of the hash lists in a 256
bucket hash table!). every d_lookup has to do the same. each inode is as
large as the largest filesystem-specific inode struct, even though most
sockets won't use any of that. all the inodes associated with sockets can
never be flushed while they have a positive reference count, which doesn't
go to zero until the socket closes (bad for high-latency connections or if
SO_LINGER is set). in current kernels, the VM system can't even ask for
inode memory back after it's been allocated to the inode cache.
think 2G of RAM is enough? :) maybe for the buffers alone...
- Chuck Lever
-- corporate: <chuckl@netscape.com> personal: <chucklever@netscape.net> or <cel@monkey.org>The Linux Scalability project: http://www.citi.umich.edu/projects/linux-scalability/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/