Re: Results of my VFS scaling evaluation.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> Certainly not for .37, where even the inode_lock splitup is pretty damn
> later.  Nick disappearing for a few weeks and others having to pick up
> the work to sort it out certainly doesn't help.  And the dcache_lock
> splitup is a much larget task than that anyway.  Getting that into .38
> is the enabler for doing more fancy things.  And as Dave mentioned at
> least in the writeback area it's much better to sort out the algorithmic
> problems now than to blindly split some locks up more.

I don't see why the algorithmic work can't be done in parallel 
to the lock split up?

Just the lock split up on its own gives us large gains here.

-Andi
-- 
ak@xxxxxxxxxxxxxxx -- Speaking for myself only.
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux