[lkml]   [2010]   [Jun]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: trying to understand READ_META, READ_SYNC, WRITE_SYNC & co
Jens Axboe <> writes:

> On 2010-06-21 11:48, Christoph Hellwig wrote:
>> Now how do we use these flags in the block layer?
>> The only place where we ever use this flag is inside the
>> cfq scheduler. In cfq_choose_req we use it to give a meta
>> request priority over one that doesn't have it. But before
>> that we already do the same preference check with rw_is_sync,
>> which evaluates to true for requests with that are either
>> reads or have REQ_SYNC set. So for reads the REQ_META flag
>> here effectively is a no-op, and for writes it gives less
>> priority than REQ_SYNC.
>> In addition to that we use it to account for pending metadata
>> requests in cfq_rq_enqueued/cfq_remove_request which gets
>> checked in cfq_should_preempt to give priority to a meta
>> request if the other queue doesn't have any pending meta
>> requests. But again this priority comes after a similar
>> check for sync requests that checks if the other queue has
>> been marked to have sync requests pending.
> It's also annotation for blktrace, so you can tell which parts of the IO
> is meta data etc. The scheduler impact is questionable, I doubt it makes
> a whole lot of difference.

Really? Even after I showed the performance impact of setting that bit
for journal I/O?


 \ /
  Last update: 2010-06-21 20:55    [W:0.102 / U:5.072 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site