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 F2D77EB64DC for ; Tue, 11 Jul 2023 12:01:24 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229576AbjGKMBX (ORCPT ); Tue, 11 Jul 2023 08:01:23 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41632 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229583AbjGKMBV (ORCPT ); Tue, 11 Jul 2023 08:01:21 -0400 Received: from bombadil.infradead.org (bombadil.infradead.org [IPv6:2607:7c80:54:3::133]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 789B6E67; Tue, 11 Jul 2023 05:01:19 -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=yL09riI3y2n7lRul4VrDuI7HTYzktNv07GtSRsYL7t0=; b=Omnd3pZ13VQdAteE+/Wl+iFWbD 4excywY3qxL8o1WqTyXY4FDWTEtJTLxouePME3G33IwRJvYNzGCznkmODhlCqy2NlQzfACxdeDjPm 07Uo/JYMEoa+udinX5d+QvhXwp5ebyRLZrqicaS6oLQXD7tET3mXxm+zvYFEIuip4bh2nJYiINHgG URa3jcgXMEQ+axzow1RWPz0KkfgG8/4Eiz4OxCUHhGLmLXHq7lY9V0DegC/FTt1OxWzXKhBBMcFgb wolUm0m8RtdJcv1I8sScDud3bM9sUWEoB2A203kC0akCTyMQPJ54c4Rg/AbdSwtteQhqxG+pzRocn FUt+NvjA==; Received: from hch by bombadil.infradead.org with local (Exim 4.96 #2 (Red Hat Linux)) id 1qJC3P-00Eoef-0m; Tue, 11 Jul 2023 12:01:15 +0000 Date: Tue, 11 Jul 2023 05:01:15 -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: <51b660f3-8145-d35e-87b4-d9ac0623606d@kernel.org> <87a5w3ymff.fsf@metaspace.dk> <875y6qzufc.fsf@metaspace.dk> <871qhezr4d.fsf@metaspace.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <871qhezr4d.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 12:15:18PM +0200, Andreas Hindborg (Samsung) wrote: > And yet they are somewhat similar, in the sense that they allow the user > of a protocol to express semantics that is not captured in the > established protocol. Uring command passthrough -> request passthrough > -> vendor specific commands. They sort of map well in terms of what they > allow the user to achieve. Or did I misunderstand something completely? Well, there is a relationship, but it's one way. Vendor specific command are basically always going to be used through a passthrough interface, because they aren't standardized. But most commands used through a passthrough interface are normal standardized commands, just either used in a way not supported by the normal Linux interface or just in creative ways.