| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20150610073526.GA6964@infradead.org> Date: Wed, 10 Jun 2015 00:35:26 -0700 From: Christoph Hellwig <hch@...radead.org> To: Ming Lei <ming.lei@...onical.com> Cc: linux-kernel@...r.kernel.org, Dave Kleikamp <dave.kleikamp@...cle.com>, Jens Axboe <axboe@...nel.dk>, Zach Brown <zab@...bo.net>, Christoph Hellwig <hch@...radead.org>, Maxim Patlasov <mpatlasov@...allels.com>, Andrew Morton <akpm@...ux-foundation.org>, Alexander Viro <viro@...iv.linux.org.uk>, Tejun Heo <tj@...nel.org>, Dave Chinner <david@...morbit.com> Subject: Re: [PATCH v5 1/5] fs: direct-io: don't dirtying pages for ITER_BVEC/ITER_KVEC direct read On Tue, Jun 09, 2015 at 09:49:22PM +0800, Ming Lei wrote: > When direct read IO is submitted from kernel, it is often > unnecessary to dirty pages, for example of loop, dirtying pages > have been considered in the upper filesystem(over loop) side > already, and they don't need to be dirtied again. > > So this patch doesn't dirtying pages for ITER_BVEC/ITER_KVEC > direct read, and loop should be the 1st case to use ITER_BVEC/ITER_KVEC > for direct read I/O. > > The patch is based on previous Dave's patch. Looks good, thanks! Reviewed-by: Christoph Hellwig <hch@....de> -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists