lkml.org 
[lkml]   [2002]   [May]   [10]   [last100]   RSS Feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
/
DateFri, 10 May 2002 09:21:14 +0200
FromJens Axboe <>
SubjectRe: O_DIRECT performance impact on 2.4.18 (was: Re: [PATCH] 2.5.14IDE 56)
On Fri, May 10 2002, Andrew Morton wrote:
> > given there's still lots of idle-time, i'll file up lockmeter on here and
> > see if theres any gremlins there.
> 
> lockmeter will go off the dial.  All those copies happen at
> interrupt time, inside the global io_request_lock.  It's horrid.

Depends. For IDE, that is so. For SCSI, actually no io_request_lock is
not held while doing the bounce copy. The write bounce copy never
happens with io_request_lock held for either, the copy-back on reads
only does if the caller holds io_request_lock while entering
end_that_request_first() (or its own replacement, __scsi_end_request()
for instance).

The read copy-back is nasty for most users regardless of io_request_lock
status, because it happens with interrupts disabled.

> Try it with the block-highmem patch:
>  http://www.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.19pre1aa1/00_block-highmem-all-18b-4.gz

That's good advise :-)

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

\
 
 \ /
  Last update: 2005-03-22 13:26    [from the cache]
©2003-2008