Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp8794531imu; Thu, 15 Nov 2018 18:14:13 -0800 (PST) X-Google-Smtp-Source: AJdET5eqnryxHFSRLPOReLaXNx2RztPEj+Zte7mo+I05WWIGT20G2a1bHayDv9w9/sNN8/nHsiB8 X-Received: by 2002:a17:902:4a0c:: with SMTP id w12-v6mr8744046pld.63.1542334453738; Thu, 15 Nov 2018 18:14:13 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1542334453; cv=none; d=google.com; s=arc-20160816; b=v2G1uveySV1LjvQdT2WN2ls6Ae36Rg8nE5ECorJS7ZQFjTs/cKVt/M5LA0jkyItMHI doR4cR58RA5blmAcolRTy4m6CjsNMLxvuF7dr+ZfFFY4fI+SzKP2NcnZ3UgQhqCeTrcL CWoXXGUyd3ZnIneSRxHTUrIXMIMWQGDtGRSxDqGYOzhB0V6/AlINU3UAeFqcoFJmKGOj rOvaT051Kvw6DwTp582lPlwlzFmEPOPmb1X2tDKMnAJwamN/KG+4KoRcGg5nnMNofU8Q Sy3VIsaERUSryVesK2ApVOPeh04giSJNF1SisLq69xmauXySucWFGI2tFe9H5BY89Irn 0DDQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=fw5ouGiFQ8H9xz3HMkj3MnFIB/8cu61F/BMbgak5qVo=; b=m+afN9cT+ZcJaJpiffY47J84QbB55nY29x9hr2z18/Ua3U5bhX4Tqe4Qt9H/EgOzNL 77AYlMmmuyOOK/xhM+xoYlDgMQdi7uzQwPGOp8hNgsLMJcR7pM4rZpaLwmq+lwwUnlcb go+fKKRYRfjPvMehp1Ojk/LXJzvLYp8QAuuv26ID1GTKZebtoKRptK+iV6QJ/JEMEtkj ciicWWh7zojNgNZI8ybiZkdXFq/jEIGVLsmHrmNbQTM73GvPjkV+zJNZZr5azpXkoMG7 aRf/3rlcjCITeQhhBp4SxhDG5BdbfEQxiRS94zuzwRgoF4eiO742Q65EF05gEIPKhB/e lcHg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@osandov-com.20150623.gappssmtp.com header.s=20150623 header.b=n43+lbPG; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m12-v6si19724463pfi.286.2018.11.15.18.13.59; Thu, 15 Nov 2018 18:14:13 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@osandov-com.20150623.gappssmtp.com header.s=20150623 header.b=n43+lbPG; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389368AbeKPMWL (ORCPT + 99 others); Fri, 16 Nov 2018 07:22:11 -0500 Received: from mail-pf1-f194.google.com ([209.85.210.194]:46125 "EHLO mail-pf1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2389343AbeKPMWL (ORCPT ); Fri, 16 Nov 2018 07:22:11 -0500 Received: by mail-pf1-f194.google.com with SMTP id s9-v6so10596689pfm.13 for ; Thu, 15 Nov 2018 18:11:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=osandov-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=fw5ouGiFQ8H9xz3HMkj3MnFIB/8cu61F/BMbgak5qVo=; b=n43+lbPGeaGJv5nZPtjvUNU9RusoWxagZQZh2JUDk5ifS+opUrvbJTg3olvONSVLlO ou399InyV5fk0IzEkS4W6JY1CeRJA2LGv9AFhCSbZDGmqqkyu1bFMLye+Gu9w7TA/jcR JWidLK99zYGxNywyV0gz2oqvqUlEmVZ2r6LNwyzVQjJI0+YbtAuhTzMTjwjO4lt3JYog B4wDn0wG+TFfi8ha98IRF+DhZW8KR8ngaM3/poOZkRLwt1d1PLOI9+YAmvFq6zyuBYCQ vLeObpH0P3IxYwopAfD5tyPJMCATwrFNrN4T08PDDJhGtKW5F0skZ1itK2BvlqWWCTwv haSQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=fw5ouGiFQ8H9xz3HMkj3MnFIB/8cu61F/BMbgak5qVo=; b=SyWIzAsnHL1O822dMZwjE8ePBAJcH218zES+O20JuEL4LI1D4WYXa3Y/lY55OoUic+ vfOitucm7KujRSkQMMbc8Ty+bhEhPalPtRQSbqRu5tdkw/uQf+fWcd3wj1kSIlaq6Oe6 y+XyKrxcJ1h8zbx+Wkdy588A6Cs1LLmWUWtozVeTiPhVN9Yd8K0F0qEHHsEImsuOA/gt ONPwDMVfukYK3nKYK7ABRvaSMeWrs9sE5mCmXGPXQ7F9prEqxWBXnsSJm8bonxYJv07r uzNqR8Wc49vjsqBGWlka20q+5fqfoGQndWbHr0LlBcwSLtg53uoMIWaEEDk5OXiFohjV XoCA== X-Gm-Message-State: AGRZ1gIdpt/6raAnocZS5r4FJJRXFV7i/pBKI77EsIR4E7R6h8tn3JEM LOdtbc23+33Jyzv+nQ3sOZXvSg== X-Received: by 2002:a63:224f:: with SMTP id t15mr8135068pgm.69.1542334302454; Thu, 15 Nov 2018 18:11:42 -0800 (PST) Received: from vader ([64.114.255.97]) by smtp.gmail.com with ESMTPSA id t3sm8847311pgv.31.2018.11.15.18.11.41 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 15 Nov 2018 18:11:41 -0800 (PST) Date: Thu, 15 Nov 2018 18:11:40 -0800 From: Omar Sandoval To: Ming Lei Cc: Jens Axboe , linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, Dave Chinner , Kent Overstreet , Mike Snitzer , dm-devel@redhat.com, Alexander Viro , linux-fsdevel@vger.kernel.org, Shaohua Li , linux-raid@vger.kernel.org, linux-erofs@lists.ozlabs.org, David Sterba , linux-btrfs@vger.kernel.org, "Darrick J . Wong" , linux-xfs@vger.kernel.org, Gao Xiang , Christoph Hellwig , Theodore Ts'o , linux-ext4@vger.kernel.org, Coly Li , linux-bcache@vger.kernel.org, Boaz Harrosh , Bob Peterson , cluster-devel@redhat.com Subject: Re: [PATCH V10 17/19] block: don't use bio->bi_vcnt to figure out segment number Message-ID: <20181116021140.GL23828@vader> References: <20181115085306.9910-1-ming.lei@redhat.com> <20181115085306.9910-18-ming.lei@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181115085306.9910-18-ming.lei@redhat.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Nov 15, 2018 at 04:53:04PM +0800, Ming Lei wrote: > It is wrong to use bio->bi_vcnt to figure out how many segments > there are in the bio even though CLONED flag isn't set on this bio, > because this bio may be splitted or advanced. > > So always use bio_segments() in blk_recount_segments(), and it shouldn't > cause any performance loss now because the physical segment number is figured > out in blk_queue_split() and BIO_SEG_VALID is set meantime since > bdced438acd83ad83a6c ("block: setup bi_phys_segments after splitting"). > > Cc: Dave Chinner > Cc: Kent Overstreet > Fixes: 7f60dcaaf91 ("block: blk-merge: fix blk_recount_segments()") From what I can tell, the problem was originally introduced by 76d8137a3113 ("blk-merge: recaculate segment if it isn't less than max segments") Is that right? > Cc: Mike Snitzer > Cc: dm-devel@redhat.com > Cc: Alexander Viro > Cc: linux-fsdevel@vger.kernel.org > Cc: Shaohua Li > Cc: linux-raid@vger.kernel.org > Cc: linux-erofs@lists.ozlabs.org > Cc: David Sterba > Cc: linux-btrfs@vger.kernel.org > Cc: Darrick J. Wong > Cc: linux-xfs@vger.kernel.org > Cc: Gao Xiang > Cc: Christoph Hellwig > Cc: Theodore Ts'o > Cc: linux-ext4@vger.kernel.org > Cc: Coly Li > Cc: linux-bcache@vger.kernel.org > Cc: Boaz Harrosh > Cc: Bob Peterson > Cc: cluster-devel@redhat.com > Signed-off-by: Ming Lei > --- > block/blk-merge.c | 8 +------- > 1 file changed, 1 insertion(+), 7 deletions(-) > > diff --git a/block/blk-merge.c b/block/blk-merge.c > index cb9f49bcfd36..153a659fde74 100644 > --- a/block/blk-merge.c > +++ b/block/blk-merge.c > @@ -429,13 +429,7 @@ void blk_recalc_rq_segments(struct request *rq) > > void blk_recount_segments(struct request_queue *q, struct bio *bio) > { > - unsigned short seg_cnt; > - > - /* estimate segment number by bi_vcnt for non-cloned bio */ > - if (bio_flagged(bio, BIO_CLONED)) > - seg_cnt = bio_segments(bio); > - else > - seg_cnt = bio->bi_vcnt; > + unsigned short seg_cnt = bio_segments(bio); > > if (test_bit(QUEUE_FLAG_NO_SG_MERGE, &q->queue_flags) && > (seg_cnt < queue_max_segments(q))) > -- > 2.9.5 >