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 66FD8C433EF for ; Thu, 27 Jan 2022 19:58:56 +0000 (UTC) Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-628-zObeovjjN4qFmNBC2oGvJA-1; Thu, 27 Jan 2022 14:58:51 -0500 X-MC-Unique: zObeovjjN4qFmNBC2oGvJA-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 36E4418B613A; Thu, 27 Jan 2022 19:58:47 +0000 (UTC) Received: from colo-mx.corp.redhat.com (colo-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.20]) by smtp.corp.redhat.com (Postfix) with ESMTPS id B01316107E; Thu, 27 Jan 2022 19:58:46 +0000 (UTC) Received: from lists01.pubmisc.prod.ext.phx2.redhat.com (lists01.pubmisc.prod.ext.phx2.redhat.com [10.5.19.33]) by colo-mx.corp.redhat.com (Postfix) with ESMTP id 4F2601809CB8; Thu, 27 Jan 2022 19:58:45 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.rdu2.redhat.com [10.11.54.8]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id 20RJwh9Q008531 for ; Thu, 27 Jan 2022 14:58:43 -0500 Received: by smtp.corp.redhat.com (Postfix) id 2EBABC23DCF; Thu, 27 Jan 2022 19:58:43 +0000 (UTC) Received: from mimecast-mx02.redhat.com (mimecast10.extmail.prod.ext.rdu2.redhat.com [10.11.55.26]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 2AAE9C23DCE for ; Thu, 27 Jan 2022 19:58:42 +0000 (UTC) Received: from us-smtp-1.mimecast.com (us-smtp-delivery-1.mimecast.com [207.211.31.120]) (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 DBE011C05B0A for ; Thu, 27 Jan 2022 19:58:42 +0000 (UTC) Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-507-GiKbDJ-BMiyqSXcY2aEZZA-1; Thu, 27 Jan 2022 14:58:38 -0500 X-MC-Unique: GiKbDJ-BMiyqSXcY2aEZZA-1 Received: by verein.lst.de (Postfix, from userid 2407) id BC25D68AA6; Thu, 27 Jan 2022 20:58:34 +0100 (CET) Date: Thu, 27 Jan 2022 20:58:34 +0100 From: Christoph Hellwig To: Mike Snitzer Message-ID: <20220127195834.GA25235@lst.de> References: <20220127063546.1314111-1-hch@lst.de> MIME-Version: 1.0 In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) 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.8 X-loop: dm-devel@redhat.com Cc: Jens Axboe , Philipp Reisner , Pavel Begunkov , linux-block@vger.kernel.org, dm-devel@redhat.com, Lars Ellenberg , Christoph Hellwig , drbd-dev@lists.linbit.com Subject: Re: [dm-devel] improve the bio cloning interface X-BeenThere: dm-devel@redhat.com X-Mailman-Version: 2.1.12 Precedence: junk List-Id: device-mapper development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 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 Thu, Jan 27, 2022 at 11:52:51AM -0500, Mike Snitzer wrote: > I'd like to take a closer look, do you happen to have this series > available in a git branch? git://git.infradead.org/users/hch/block.git bio_alloc-cleanup-part2 > > The changes generally look fine. Any chance you could forecast what > you're planning for follow-on changes? Mostly cleaning up a bunch of submitter code that needs more work to get at the bdev and op, and trying to figure out what to do about bio_kmalloc. > Or is it best to just wait for you to produce those follow-on changes? There should be no follow ons required to make sense of this series. -- 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 6EA25C433F5 for ; Thu, 27 Jan 2022 19:58:39 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1343531AbiA0T6i (ORCPT ); Thu, 27 Jan 2022 14:58:38 -0500 Received: from verein.lst.de ([213.95.11.211]:45638 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1343516AbiA0T6i (ORCPT ); Thu, 27 Jan 2022 14:58:38 -0500 Received: by verein.lst.de (Postfix, from userid 2407) id BC25D68AA6; Thu, 27 Jan 2022 20:58:34 +0100 (CET) Date: Thu, 27 Jan 2022 20:58:34 +0100 From: Christoph Hellwig To: Mike Snitzer Cc: Christoph Hellwig , Jens Axboe , Pavel Begunkov , Philipp Reisner , Lars Ellenberg , linux-block@vger.kernel.org, dm-devel@redhat.com, drbd-dev@lists.linbit.com Subject: Re: improve the bio cloning interface Message-ID: <20220127195834.GA25235@lst.de> References: <20220127063546.1314111-1-hch@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-block@vger.kernel.org On Thu, Jan 27, 2022 at 11:52:51AM -0500, Mike Snitzer wrote: > I'd like to take a closer look, do you happen to have this series > available in a git branch? git://git.infradead.org/users/hch/block.git bio_alloc-cleanup-part2 > > The changes generally look fine. Any chance you could forecast what > you're planning for follow-on changes? Mostly cleaning up a bunch of submitter code that needs more work to get at the bdev and op, and trying to figure out what to do about bio_kmalloc. > Or is it best to just wait for you to produce those follow-on changes? There should be no follow ons required to make sense of this series. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by mail19.linbit.com (LINBIT Mail Daemon) with ESMTP id 5C45D42A583 for ; Thu, 27 Jan 2022 20:58:37 +0100 (CET) Date: Thu, 27 Jan 2022 20:58:34 +0100 From: Christoph Hellwig To: Mike Snitzer Message-ID: <20220127195834.GA25235@lst.de> References: <20220127063546.1314111-1-hch@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: Jens Axboe , Philipp Reisner , Pavel Begunkov , linux-block@vger.kernel.org, dm-devel@redhat.com, Lars Ellenberg , Christoph Hellwig , drbd-dev@lists.linbit.com Subject: Re: [Drbd-dev] improve the bio cloning interface List-Id: "*Coordination* of development, patches, contributions -- *Questions* \(even to developers\) go to drbd-user, please." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, Jan 27, 2022 at 11:52:51AM -0500, Mike Snitzer wrote: > I'd like to take a closer look, do you happen to have this series > available in a git branch? git://git.infradead.org/users/hch/block.git bio_alloc-cleanup-part2 > > The changes generally look fine. Any chance you could forecast what > you're planning for follow-on changes? Mostly cleaning up a bunch of submitter code that needs more work to get at the bdev and op, and trying to figure out what to do about bio_kmalloc. > Or is it best to just wait for you to produce those follow-on changes? There should be no follow ons required to make sense of this series.