Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp516339imu; Mon, 26 Nov 2018 14:15:42 -0800 (PST) X-Google-Smtp-Source: AFSGD/X8J+2e7sh+xKReHkRFSemmlpI60sE3rlNVDog+kHr1l1t9Zbsk76w0iXYS458tWfV1pNfg X-Received: by 2002:a63:604f:: with SMTP id u76mr23733154pgb.401.1543270542188; Mon, 26 Nov 2018 14:15:42 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1543270542; cv=none; d=google.com; s=arc-20160816; b=wTP/Zel2e4TOIqG109hTKsbWhRptGL6+2A2/lVjYCN3ono6/XfAzqIddYqzJny4GxI fvDaZZ4TW79pTa83+kfzUgCZtGJ7ma8JoF2OOtAm+THGUcquONxtCcGRnrWwBZuYykcl 4IdOWdYxZOuRfzRIhjrfSWGh+88UVPL5Sj6r5qk/1wwYwcSx9UHkVQi417BsAcUoynhd PTOzUFIec9Hjyj95BKKw7RjRyJDUjLWJw8yoWRKPOosXQxqWXRQz2vvMaIH3uoVEkkYF 9ROno7ktHTAUpJgwNFrmO53a7nqsI9OW7OeYZQwXeMo8hNEYoTD0BqsB8GkMAfrUzOG9 U5rQ== 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=9AkyZOjm/sng5co17bYs/2llMKYYVqfTbY1b6HL7DLY=; b=MUrfX3JA3/z0KcKRZgHIZ2X8elIPRJrTuZGAtoFpHCkSG/Kkax2P23fyn5O2aNJyJV UavP1Rrl+fld2l5CywkPdaFeqzMICrUTdMCA/kFjwDQRPTvgEccPBPvH4su71Pe/E9EC x7705h8AyBKz+UWHU9h+Ahy+KiPPdpvWUpEkXpVc5l+qZtBZn6mbt92LevXSHZC2I2tL Qtwh2BnSu/R9jdKeAI5f2DuGGuvOzOwB/DeE6HNHxy2Yc09VzajCgv2DxlHwGW5Ssp47 RhcNtGNeYI27J9jsGgPxLaEbpZzo3l84DXZ2fL8Xx/Iqfsyf4hCt2c9yR6YwvVhZUmWZ SU4g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@osandov-com.20150623.gappssmtp.com header.s=20150623 header.b=O7WNWIgz; 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 e8si1457591pgn.325.2018.11.26.14.15.26; Mon, 26 Nov 2018 14:15:42 -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=O7WNWIgz; 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 S1727289AbeK0JKZ (ORCPT + 99 others); Tue, 27 Nov 2018 04:10:25 -0500 Received: from mail-pf1-f196.google.com ([209.85.210.196]:35840 "EHLO mail-pf1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726888AbeK0JKY (ORCPT ); Tue, 27 Nov 2018 04:10:24 -0500 Received: by mail-pf1-f196.google.com with SMTP id b85so7276096pfc.3 for ; Mon, 26 Nov 2018 14:14:49 -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=9AkyZOjm/sng5co17bYs/2llMKYYVqfTbY1b6HL7DLY=; b=O7WNWIgzkXf1oK/nBoaA7B4ovU42gjQqCbUt0jqoaewwuXODvM+n28sAcfrqBN9FxF d+sCGTNY8vm9rg4JinMqrXUuXNXRMlbt1mxB1YKPSUhT4JVM7iS2IlpdA4gQ0Dbtly6B b2f7hLoWHcdQSAZNx+KRZWuj5zakI4I7SM2Qr/3tFvtVY8TpnkvNwPHrG5yJ9VGMFgtr yYMsTmf2CRSl8Pu6UI0/a3xitEaMyrgsc53AbOgHEJwUU8vUMnbYjVGEPT07Pl1LiopT aO9PKUVWDb+36q4jj+nyvSoOvdeWUlrWvviQvDDHOl9BFLYcvbShWR4hYnL9ThOjXc6n J73Q== 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=9AkyZOjm/sng5co17bYs/2llMKYYVqfTbY1b6HL7DLY=; b=X317A2X2mdhb2//Xa5URdMJE81jAwkxvvhOMYxxnO/hZLN22HuPpdncZ7VRhJbFtI0 g7LYy/jieEl2qAUXK50kRpzyj2yBjns5h6+ASzdphFYah+1oW68808kod+cwai43PAxy qxltVeWfHosbOfgubKPmKxWmgJ8FOv/xhMVmk/YWvF2OUbSxQyCPU5vUFDpRdbKGvNaD AIuA8oypt5uh6FOusSJhGH6cLFpNtLckUPvl2G6QMsMcRPyJUWC4Jaa2etcjFWOqfQH2 s8vfSR+ENv/amOZKvRO9+ELHxqZ2ZR2aF714vI/skqMi2xtR+NV2LeQaowDZ2llU4ZRx lOnA== X-Gm-Message-State: AA+aEWYLr06qwoQDAeOB+rOq3PffZ1olnQX7+vaExsgI+ph8pebBS1Lt PXLU7lgfVMK0W5WYnNqgZ/F1tA== X-Received: by 2002:a63:78cd:: with SMTP id t196mr26824599pgc.62.1543270489280; Mon, 26 Nov 2018 14:14:49 -0800 (PST) Received: from vader ([2601:602:8b00:55d3:e6a7:a0ff:fe0b:c9a8]) by smtp.gmail.com with ESMTPSA id c67sm1688753pfg.170.2018.11.26.14.14.48 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 26 Nov 2018 14:14:48 -0800 (PST) Date: Mon, 26 Nov 2018 14:14:47 -0800 From: Omar Sandoval To: Ming Lei Cc: Jens Axboe , linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, Theodore Ts'o , Omar Sandoval , Sagi Grimberg , Dave Chinner , Kent Overstreet , Mike Snitzer , dm-devel@redhat.com, Alexander Viro , linux-fsdevel@vger.kernel.org, Shaohua Li , linux-raid@vger.kernel.org, David Sterba , linux-btrfs@vger.kernel.org, "Darrick J . Wong" , linux-xfs@vger.kernel.org, Gao Xiang , Christoph Hellwig , linux-ext4@vger.kernel.org, Coly Li , linux-bcache@vger.kernel.org, Boaz Harrosh , Bob Peterson , cluster-devel@redhat.com Subject: Re: [PATCH V12 04/20] block: don't use bio->bi_vcnt to figure out segment number Message-ID: <20181126221447.GE30411@vader> References: <20181126021720.19471-1-ming.lei@redhat.com> <20181126021720.19471-5-ming.lei@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181126021720.19471-5-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 Mon, Nov 26, 2018 at 10:17:04AM +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"). > > Reviewed-by: Christoph Hellwig Reviewed-by: Omar Sandoval > Fixes: 76d8137a3113 ("blk-merge: recaculate segment if it isn't less than max segments") > 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 e69d8f8ba819..51ec6ca56a0a 100644 > --- a/block/blk-merge.c > +++ b/block/blk-merge.c > @@ -367,13 +367,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 >