From mboxrd@z Thu Jan 1 00:00:00 1970 From: Omar Sandoval Subject: Re: [PATCH v2 2/5] direct-io: don't dirty ITER_BVEC pages on read Date: Sun, 21 Dec 2014 23:12:16 -0800 Message-ID: <20141222071216.GA24722@mew> References: <20141220060130.GA22149@ZenIV.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Andrew Morton , Trond Myklebust , Christoph Hellwig , linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org, Ming Lei To: Al Viro Return-path: Content-Disposition: inline In-Reply-To: <20141220060130.GA22149@ZenIV.linux.org.uk> Sender: owner-linux-mm@kvack.org List-Id: linux-fsdevel.vger.kernel.org On Sat, Dec 20, 2014 at 06:01:30AM +0000, Al Viro wrote: > On Fri, Dec 19, 2014 at 07:18:26PM -0800, Omar Sandoval wrote: > > Reads through the iov_iter infrastructure for kernel pages shouldn't be > > dirtied by the direct I/O code. > > > > This is based on Dave Kleikamp's and Ming Lei's previously posted > > patches. > > Umm... > > > + dio->should_dirty = !iov_iter_is_bvec(iter); > > dio->should_dirty = iter_is_iovec(iter); > > perhaps? Mm, yeah, I'll do that. That helper snuck in without me noticing it... I see that we can't do iov_iter_get_pages on an ITER_KVEC, so a kvec doesn't work for blockdev_direct_IO anyways, right? -- Omar -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org