2.5.21 IDE 91
Quoted 5 lines
Quoted 3 lines
Quoted 1 line
test the crap out of a kernel :).
Linux Test Project's
runalltests.shhas occasionally triggered a bug.Is this still happening? What was the bug?
That's just a general suggestion with regard to kernel testing. Recent 2.5.x hasn't had a problem completing LTP runalltests.sh. I've used LTP to narrow down a couple early 2.4.x reiserfs bugs to a specific test case. LTP has occasionally triggered oops and livelocks too. It's a useful regression test.
Quoted 5 lines
Quoted 3 lines
2.5 took a drop in dbench throughput recently.
dbench ext2 128 processes Average High Low(MB/sec)
Is this still with 384 megs of memory?
Yes.
Quoted 10 lines
2.5.19 18.60 21.69 14.58 2.5.20 12.89 13.15 12.79One possibile culprit here is the doubling of the request queue size in 2.5.20. A long time ago it was 1024 slots. Then it went to
128. That's where it is in Marcelo kernels. Then -ac kernels went up to 1024 because they have read-latency2. Somehow 2.5 found itself at 256 slots. In 2.5.20 it slealthily snuck up to 512 slots. I didn't squeak about this because I was interested to see what effect it would have.
Interesting. I've seen read-latency2 drop dbench throughput in -aa kernels (but I use it anyway). I'd like to capture the request queue size. Is there a command or file in /proc that displays it, or should I just grep drivers/block/ll_rw_blk.c?
Quoted 1 line
Does this patch get the throughput back?
I will try that next.
Signature · 1 line
Randy Hron
Quoted 8 lines · On Sat, Jun 15 2002, [email protected] wrote:
Quoted 7 lines
One possibile culprit here is the doubling of the request queue size in 2.5.20. A long time ago it was 1024 slots. Then it went to
128. That's where it is in Marcelo kernels. Then -ac kernels went up to 1024 because they have read-latency2. Somehow 2.5 found itself at 256 slots. In 2.5.20 it slealthily snuck up to 512 slots. I didn't squeak about this because I was interested to see what effect it would have.
Quoted 4 lines
Interesting. I've seen read-latency2 drop dbench throughput in -aa kernels (but I use it anyway). I'd like to capture the request queue size. Is there a command or file in /proc that displays it, or should I just grep
drivers/block/ll_rw_blk.c?
There is currently no way you can capture the queue request state. In the past I've done sysrq hacks to display it, but that's about it.
Signature · 1 line
Jens Axboe