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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxxx  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>



[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]