On Mon 16-03-15 11:34:41, Josef Bacik wrote:
...
> >>diff --git a/fs/block_dev.c b/fs/block_dev.c
> >>index 2eb2436..d23ce6f 100644
> >>--- a/fs/block_dev.c
> >>+++ b/fs/block_dev.c
> >>@@ -1749,38 +1749,56 @@ int __invalidate_device(struct block_device *bdev,
> >>bool kill_dirty)
> >> }
> >> EX
On 03/16/2015 08:27 AM, Jan Kara wrote:
Hello,
On Tue 10-03-15 15:45:23, Josef Bacik wrote:
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
Hello,
On Tue 10-03-15 15:45:23, Josef Bacik wrote:
> 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
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 dur
4 matches
Mail list logo
