Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755349Ab3IYVRa (ORCPT ); Wed, 25 Sep 2013 17:17:30 -0400 Received: from mx1.redhat.com ([209.132.183.28]:62583 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751249Ab3IYVR3 (ORCPT ); Wed, 25 Sep 2013 17:17:29 -0400 Date: Wed, 25 Sep 2013 14:17:02 -0700 From: Zach Brown To: Kent Overstreet Cc: hch@infradead.org, axboe@kernel.dk, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/6] block: Introduce bio_for_each_page() Message-ID: <20130925211702.GH30372@lenny.home.zabbo.net> References: <1380140564-9030-1-git-send-email-kmo@daterainc.com> <1380140564-9030-2-git-send-email-kmo@daterainc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1380140564-9030-2-git-send-email-kmo@daterainc.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1069 Lines: 33 > void zero_fill_bio(struct bio *bio) > { > - unsigned long flags; > struct bio_vec bv; > struct bvec_iter iter; > > - bio_for_each_segment(bv, bio, iter) { > +#if defined(CONFIG_HIGHMEM) || defined(ARCH_IMPLEMENTS_FLUSH_DCACHE_PAGE) > + bio_for_each_page(bv, bio, iter) { > + unsigned long flags; > char *data = bvec_kmap_irq(&bv, &flags); > memset(data, 0, bv.bv_len); > flush_dcache_page(bv.bv_page); > bvec_kunmap_irq(data, &flags); > } > +#else > + bio_for_each_segment(bv, bio, iter) > + memset(page_address(bv.bv_page) + bv.bv_offset, > + 0, bv.bv_len); > +#endif This looks pretty sketchy. I'd expect this to be doable with one loop and that bvec_kmap_irq() and flush_dcache_page() would fall back to page_address() and nops when they're not needed. Where did this come from? - z -- 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/