From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.2 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id AE96AC433E1 for ; Mon, 17 Aug 2020 10:14:45 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 906912067C for ; Mon, 17 Aug 2020 10:14:45 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726165AbgHQKOp (ORCPT ); Mon, 17 Aug 2020 06:14:45 -0400 Received: from verein.lst.de ([213.95.11.211]:56127 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726151AbgHQKOo (ORCPT ); Mon, 17 Aug 2020 06:14:44 -0400 Received: by verein.lst.de (Postfix, from userid 2407) id B16CE68B02; Mon, 17 Aug 2020 12:14:41 +0200 (CEST) Date: Mon, 17 Aug 2020 12:14:41 +0200 From: Christoph Hellwig To: Ming Lei Cc: Jens Axboe , linux-block@vger.kernel.org, Christoph Hellwig Subject: Re: [PATCH V3 3/3] block: rename blk_discard_mergable as blk_discard_support_multi_range Message-ID: <20200817101441.GA25336@lst.de> References: <20200817095241.2494763-1-ming.lei@redhat.com> <20200817095241.2494763-4-ming.lei@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200817095241.2494763-4-ming.lei@redhat.com> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-block-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-block@vger.kernel.org On Mon, Aug 17, 2020 at 05:52:41PM +0800, Ming Lei wrote: > Name of blk_discard_mergable() is very confusing, and this function > actually means if the queue supports multi_range discard. Also there > are two kinds of discard merge: > > 1) multi range discard, bios in one request won't have to be contiguous, > and actually each bio is thought as one range > > 2) single range discard, all bios in one request have to be contiguous > just like normal RW request's merge > > Rename blk_discard_mergable() for not confusing people, and avoiding > to introduce bugs in future. I agree the current name is not good, but I find the new one pretty clumsy too. Not sure the rename is worth it, but also no strict NAK from me.