Zach Brown <zach.brown@xxxxxxxxxx> writes: > This adds a high level entry point into the direct-io code which calls helpers > on memory specified by pages instead of iovecs. > > curr_user_address is used to decide if we should be dirtying the memory pages. > In our case, we don't want to. > > The trick here is to initialize the dio state so that do_direct_IO() consumes > the pages we provide and never tries to map user pages. This is done by making > sure that final_block_in_request covers all the pages we provide. Looks sane, in general. > - if (dio->is_async && dio->rw == READ) > + if (dio->is_async && dio->rw == READ && dio->curr_user_address) Any chance we can factor this check out into a macro or some such thing? It's repeated several times. Cheers, Jeff -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
