Messages in this thread | | | Date | Sat, 15 Mar 2003 04:25:47 -0800 | From | William Lee Irwin III <> | Subject | Re: [PATCH] concurrent block allocation for ext2 against 2.5.64 |
| |
On Sat, Mar 15, 2003 at 12:24:31AM -0800, William Lee Irwin III wrote: >> Okay, dump_stack() every once in a while when we schedule() in down().
On Sat, Mar 15, 2003 at 04:08:19AM -0800, Andrew Morton wrote: > Thanks.
No problem. I think we found out a number of things that help everyone.
On Sat, Mar 15, 2003 at 12:24:31AM -0800, William Lee Irwin III wrote: >> No good ideas how to script the results so I have the foggiest idea >> who's the bad guy. gzipped and MIME attached (Sorry!) for space reasons.
On Sat, Mar 15, 2003 at 04:08:19AM -0800, Andrew Morton wrote: > lock_super() in the ext2 inode allocator mainly. It needs the same treatment.
Terrific! Not only have we resolved 16x ext2 contention issues we've also identified a clear direction for 32x!!
Go fs hackers go! First 2.5 VM, now 2.6/2.7 VFS. What can't you do?
-- wli - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |