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 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 043DFC433F5 for ; Sat, 9 Apr 2022 05:16:00 +0000 (UTC) Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-2-d4SxsqCsMCSGfQIICWYfQw-1; Sat, 09 Apr 2022 01:15:56 -0400 X-MC-Unique: d4SxsqCsMCSGfQIICWYfQw-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com [10.11.54.4]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 5B77785A5BC; Sat, 9 Apr 2022 05:15:54 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com [10.30.29.100]) by smtp.corp.redhat.com (Postfix) with ESMTP id 0B5812026987; Sat, 9 Apr 2022 05:15:54 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (localhost [IPv6:::1]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 608021940349; Sat, 9 Apr 2022 05:15:51 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx10.intmail.prod.int.rdu2.redhat.com [10.11.54.10]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id C4D471940341 for ; Sat, 9 Apr 2022 05:15:50 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id 6592B41637F; Sat, 9 Apr 2022 05:15:50 +0000 (UTC) Received: from mimecast-mx02.redhat.com (mimecast04.extmail.prod.ext.rdu2.redhat.com [10.11.55.20]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 6191041637D for ; Sat, 9 Apr 2022 05:15:50 +0000 (UTC) Received: from us-smtp-1.mimecast.com (us-smtp-2.mimecast.com [207.211.31.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 46A8A101A52C for ; Sat, 9 Apr 2022 05:15:50 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-593-DOckbprLPCqavdgC4DDjJA-1; Sat, 09 Apr 2022 01:15:48 -0400 X-MC-Unique: DOckbprLPCqavdgC4DDjJA-1 Received: from hch by bombadil.infradead.org with local (Exim 4.94.2 #2 (Red Hat Linux)) id 1nd3Rl-002DAU-Bg; Sat, 09 Apr 2022 05:15:41 +0000 Date: Fri, 8 Apr 2022 22:15:41 -0700 From: Christoph Hellwig To: Mike Snitzer Message-ID: References: MIME-Version: 1.0 In-Reply-To: X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org. See http://www.infradead.org/rpr.html X-Mimecast-Impersonation-Protect: Policy=CLT - Impersonation Protection Definition; Similar Internal Domain=false; Similar Monitored External Domain=false; Custom External Domain=false; Mimecast External Domain=false; Newly Observed Domain=false; Internal User Name=false; Custom Display Name List=false; Reply-to Address Mismatch=false; Targeted Threat Dictionary=false; Mimecast Threat Dictionary=false; Custom Threat Dictionary=false X-Scanned-By: MIMEDefang 2.85 on 10.11.54.10 Subject: Re: [dm-devel] can we reduce bio_set_dev overhead due to bio_associate_blkg? X-BeenThere: dm-devel@redhat.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: device-mapper development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: axboe@kernel.dk, linux-block@vger.kernel.org, Mike Snitzer , Christoph Hellwig , dm-devel@redhat.com, tj@kernel.org, Dennis Zhou Errors-To: dm-devel-bounces@redhat.com Sender: "dm-devel" X-Scanned-By: MIMEDefang 2.78 on 10.11.54.4 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=dm-devel-bounces@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Fri, Apr 08, 2022 at 11:42:51AM -0400, Mike Snitzer wrote: > I think we can achieve the goal of efficient cloning/remapping for > both usecases simply by splitting out the bio_set_dev() and leaving it > to the caller to pick which interface to use (e.g. clone vs > clone_and_remap). You can just pass a NULL bdev to bio_alloc_clone/bio_init_clone. I've been hoping to get rid of that, but if we have a clear use case it will have to stay. -- dm-devel mailing list dm-devel@redhat.com https://listman.redhat.com/mailman/listinfo/dm-devel 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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9FE22C433EF for ; Sat, 9 Apr 2022 05:15:48 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229701AbiDIFRw (ORCPT ); Sat, 9 Apr 2022 01:17:52 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37956 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232130AbiDIFRv (ORCPT ); Sat, 9 Apr 2022 01:17:51 -0400 Received: from bombadil.infradead.org (bombadil.infradead.org [IPv6:2607:7c80:54:e::133]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 691C826129 for ; Fri, 8 Apr 2022 22:15:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20210309; h=In-Reply-To:Content-Type:MIME-Version :References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=v5AUaXmXbfF5lrBdpvkZcFbAxCun5fHL446CBq+qPn4=; b=3yzv0B+b5AiWTVUvxQOp6I5XfM 7te3Z0QZ9NjotZL9XDb9lV/pQObdOzPM/gU5a4EkihalsNWIwO091pEBsRO1LmbQEkhYatEmv8qcc uDIPhnp0Hc98F0lXlT4j4MUtqqqMEOrXNIalVA9lydLwXsUL3KmmXg/9DvJlth1Q2D7NYqUHPI1FU F66XDI/AFfUFtiofXf0861VcJt379gJMkuGLOCyhDnurMzR+86P1b6z0qj6gVZIk4xq6gHkoHKQNU iRHQCxoQ+HzDEDcAkFRj88nHpLzBjjp/wBMfuv0Pid7m5W0CdXDmJpecq56i7RqOPwaz/A7ZB9gEq /rFHiIpA==; Received: from hch by bombadil.infradead.org with local (Exim 4.94.2 #2 (Red Hat Linux)) id 1nd3Rl-002DAU-Bg; Sat, 09 Apr 2022 05:15:41 +0000 Date: Fri, 8 Apr 2022 22:15:41 -0700 From: Christoph Hellwig To: Mike Snitzer Cc: Christoph Hellwig , Dennis Zhou , Mike Snitzer , tj@kernel.org, axboe@kernel.dk, linux-block@vger.kernel.org, dm-devel@redhat.com Subject: Re: can we reduce bio_set_dev overhead due to bio_associate_blkg? Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org. See http://www.infradead.org/rpr.html Precedence: bulk List-ID: X-Mailing-List: linux-block@vger.kernel.org On Fri, Apr 08, 2022 at 11:42:51AM -0400, Mike Snitzer wrote: > I think we can achieve the goal of efficient cloning/remapping for > both usecases simply by splitting out the bio_set_dev() and leaving it > to the caller to pick which interface to use (e.g. clone vs > clone_and_remap). You can just pass a NULL bdev to bio_alloc_clone/bio_init_clone. I've been hoping to get rid of that, but if we have a clear use case it will have to stay.