Re: [patch] zero-bounce block highmem I/O, #13

• Next message: Roman Zippel: "Re: [IDEA+RFC] Possible solution for min()/max() war"
• Previous message: Christian Borntraeger: "re: VM: Bad swap entry 0044cb00"
• In reply to: Christoph Rohland: "Re: [patch] zero-bounce block highmem I/O, #13"
• Next in thread: Christoph Rohland: "Re: [patch] zero-bounce block highmem I/O, #13"
• Reply: Christoph Rohland: "Re: [patch] zero-bounce block highmem I/O, #13"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Tue, Aug 28 2001, Christoph Rohland wrote:
> Hi Jens,
>
> On Tue, 28 Aug 2001, Jens Axboe wrote:
> > Ok found the bug -- SCSI was accidentally using blk_seg_merge_ok
> > when it just wanted to test if we were crossing a 4GB physical
> > address boundary or not. Doh! Attached incremental patch should fix
> > the SCSI performance issue. I'm testing right now...
>
> Yup, performance is back to 2.4.9 level. But I do not see an
> improvement.
>
> I will now do a database import.

Of course it depends on the type of work load how big an improvement you
see. How much RAM is in the machine?

It would be interesting to see profiles of stock + highmem kernels.

-- 
Jens Axboe
-
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/

• Next message: Roman Zippel: "Re: [IDEA+RFC] Possible solution for min()/max() war"
• Previous message: Christian Borntraeger: "re: VM: Bad swap entry 0044cb00"
• In reply to: Christoph Rohland: "Re: [patch] zero-bounce block highmem I/O, #13"
• Next in thread: Christoph Rohland: "Re: [patch] zero-bounce block highmem I/O, #13"
• Reply: Christoph Rohland: "Re: [patch] zero-bounce block highmem I/O, #13"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Fri Aug 31 2001 - 21:00:28 EST