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 CD0DCEB64DC for ; Tue, 11 Jul 2023 08:22:14 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229917AbjGKIWN (ORCPT ); Tue, 11 Jul 2023 04:22:13 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41626 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229573AbjGKIWM (ORCPT ); Tue, 11 Jul 2023 04:22:12 -0400 Received: from bombadil.infradead.org (bombadil.infradead.org [IPv6:2607:7c80:54:3::133]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8890191; Tue, 11 Jul 2023 01:22:09 -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=Qwuo2cmnOyKWMhs51uip+VVO1uccisKrt4zrIgmUcvQ=; b=jvp1svZdBq8Y4YpYYuoVxg/q8n a9UCIH+MHHb5EXp3PuUPDhv0FhMYQ+wW+pAb2oaf9mijPY66kxtbP9rsiowfWLKrdmoDtmcVDSNOd rNDvx0Sgy46rh9bvIHhshESc/FlazgPHAJY8NJqRKLKFX9mqPVGSiJNbA40UTI9xwgCarfkXXn8pz a5N1EPYo5FrfSPCVg5yw1BmC8Ly5BAwzcRW01/w0QeKMeTdVjQpvk7kg99HLYWrGYChUE4RdZZgvz rreBNt7M11s1ncS93G60LwDE0ndJeX2f3SV9MdsJZyYwSQ2C0SCZWQiHsO3nZwGYSIVyRwA4BeWOL 8E44roig==; Received: from hch by bombadil.infradead.org with local (Exim 4.96 #2 (Red Hat Linux)) id 1qJ8dG-00E5jN-1N; Tue, 11 Jul 2023 08:22:02 +0000 Date: Tue, 11 Jul 2023 01:22:02 -0700 From: Christoph Hellwig To: "Andreas Hindborg (Samsung)" Cc: Christoph Hellwig , Ming Lei , Damien Le Moal , open list , "open list:BLOCK LAYER" , Minwoo Im , Matias Bjorling , gost.dev@samsung.com, Jens Axboe , Aravind Ramesh , Johannes Thumshirn , Hans Holmberg Subject: Re: [PATCH v6 1/3] ublk: add opcode offsets for DRV_IN/DRV_OUT Message-ID: References: <20230706130930.64283-1-nmi@metaspace.dk> <20230706130930.64283-2-nmi@metaspace.dk> <51b660f3-8145-d35e-87b4-d9ac0623606d@kernel.org> <87a5w3ymff.fsf@metaspace.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87a5w3ymff.fsf@metaspace.dk> 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 Tue, Jul 11, 2023 at 08:23:40AM +0200, Andreas Hindborg (Samsung) wrote: > Yet most on-the-wire protocols for actual hardware does support this > some way or another. Supports what? Passthrough? No. > I somewhat agree in the sense that for consistency, we should either > move zone management commands to the DRV_OUT range OR move report_zones > out of this special range and just next to the zone management > operations. I like the latter option better, and I would love to see the > block layer do the same at some point. It feels backwards that > report_zones get special treatment all over the place. DRV_IN/OUT is purely a Linux concept. It doesn't make any sense for a wire protocol.