On Thu, Aug 01, 2013 at 01:19:50AM -0700, Christoph Hellwig wrote:
> At this point the list_lru name really becomes confusing. Given that
> it's not really LRU specific maybe just rename it to pernode_list
> or similar?
Well, such things were suggested when the list_lru was first
proposed.
At this point the list_lru name really becomes confusing. Given that
it's not really LRU specific maybe just rename it to pernode_list
or similar?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info
At this point the list_lru name really becomes confusing. Given that
it's not really LRU specific maybe just rename it to pernode_list
or similar?
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On Thu, Aug 01, 2013 at 01:19:50AM -0700, Christoph Hellwig wrote:
At this point the list_lru name really becomes confusing. Given that
it's not really LRU specific maybe just rename it to pernode_list
or similar?
Well, such things were suggested when the list_lru was first
proposed. Indeed,
From: Dave Chinner
The per-superblock inode list and lock is a bottleneck for systems
that cycle inodes in and out of cache concurrently. The global lock
is a limiting factor.
Most of the additions to the sb inode list occur on the CPU that
allocated the inode, and most of the removals occur
From: Dave Chinner dchin...@redhat.com
The per-superblock inode list and lock is a bottleneck for systems
that cycle inodes in and out of cache concurrently. The global lock
is a limiting factor.
Most of the additions to the sb inode list occur on the CPU that
allocated the inode, and most of
6 matches
Mail list logo