Messages in this thread | | | Date | Sat, 15 Mar 2003 04:08:19 -0800 | From | Andrew Morton <> | Subject | Re: [PATCH] concurrent block allocation for ext2 against 2.5.64 |
| |
William Lee Irwin III <wli@holomorphy.com> wrote: > > On Sat, Mar 15, 2003 at 12:24:31AM -0800, William Lee Irwin III wrote: > >> Next pass involves lockmeter: > > On Sat, Mar 15, 2003 at 01:47:58AM -0800, William Lee Irwin III wrote: > > Throughput 39.2014 MB/sec 128 procs > > dbench 128 142.51s user 10828.91s system 964% cpu 18:57.88 total > > That's an 83% reduction in throughput from applying lockmeter. > > Um, somebody should look into this. The thing is a bloody doorstop: > > Okay, dump_stack() every once in a while when we schedule() in down().
Thanks.
> 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.
lock_super() in the ext2 inode allocator mainly. It needs the same treatment.
- 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/
| |