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 5F087EB64DD for ; Tue, 11 Jul 2023 10:20:55 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230180AbjGKKUy (ORCPT ); Tue, 11 Jul 2023 06:20:54 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52408 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229626AbjGKKUu (ORCPT ); Tue, 11 Jul 2023 06:20:50 -0400 Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com [IPv6:2a00:1450:4864:20::136]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 909D5DB for ; Tue, 11 Jul 2023 03:20:48 -0700 (PDT) Received: by mail-lf1-x136.google.com with SMTP id 2adb3069b0e04-4f9fdb0ef35so8904998e87.0 for ; Tue, 11 Jul 2023 03:20:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=metaspace-dk.20221208.gappssmtp.com; s=20221208; t=1689070847; x=1691662847; h=mime-version:message-id:in-reply-to:date:subject:cc:to:from :user-agent:references:from:to:cc:subject:date:message-id:reply-to; bh=PVUO3IRo/r86ZHpIHo6p2mGssmLAdn3Wiwp1qbl6NZg=; b=l6xzQzJ0wZ34IfsIs+w4utMMGzrjS8GwYFaO5CLdqUnkpMaN/RPtIqoP1GpB7ws9jw PbC0TPm9oDF12T8GtSGP7KKpzSRNd8YnDGR7qSBwHWTd9i8mXHVpwaysRzIxUznYZrVg CsLKamLPTZJYCgl/SXxXJAWg483Smcf2MnQ2dJs6K3Y0S31P7IY7WiZNAyKNleFfJukS GqJ5m1mnfSDWDWCoXXjX2iOfnbeQOY7Y44/dOW/canQ03nqbexdTI4ciZn/btXQIHyB1 xDaAqS4WWBhvia/7Pw+grpB5hBXfltxYUOeJ6qFoTyvPVoWg5NjE+3tl2pTbWOqstfrk 40Vw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1689070847; x=1691662847; h=mime-version:message-id:in-reply-to:date:subject:cc:to:from :user-agent:references:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=PVUO3IRo/r86ZHpIHo6p2mGssmLAdn3Wiwp1qbl6NZg=; b=e+Ytln9f2xUl4vlWq2XAzzdAELsFphjFvZtFvgh3bSq8rjDq8u/SXksWXJV0uxrM5W you9zJbD1Uc5+qr8HE9JMGQEGNAjcZtmx6Wbm3YHKHBmfUfk/kXkR0fX5Qcr31C8zBZi PUWHQzb09WnLvpngacYgK5v1GTGkl7J5e1/tPAAIvHoAIy2z5VwgwQojrusomVFCK5cq OimmZfTyv2+28XI/diux3+0/ReVhRiIikv3tC7zEBWes9K3XwDp+8JjOa/FynZBeUgHi JwXuepaYf/Y6x/r86Jc89OLjXANMx8fXUEGtxHvypuAmkgC11H7bU5VtF9I5cRZQ7fns 20tg== X-Gm-Message-State: ABy/qLZQ+reKTagc1ivIe/K9/dC0sNBEU8wjV7h4AfqdOuGBvlw18sdh eXMLKX1Gz7cElSWQ1luic6jazg== X-Google-Smtp-Source: APBJJlFZ0Z9MV5Y+DZ8EwTnzHNYnhwkKaeV67mS31xGtgrw9cGJ095ievyhPP9vnRq7WKGsW2VrPww== X-Received: by 2002:a05:6512:e9c:b0:4f8:7325:bcd4 with SMTP id bi28-20020a0565120e9c00b004f87325bcd4mr14277883lfb.0.1689070846653; Tue, 11 Jul 2023 03:20:46 -0700 (PDT) Received: from localhost ([185.108.254.55]) by smtp.gmail.com with ESMTPSA id 22-20020ac24836000000b004fb12e0c3eesm254676lft.193.2023.07.11.03.20.46 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 11 Jul 2023 03:20:46 -0700 (PDT) References: <20230706130930.64283-1-nmi@metaspace.dk> <20230706130930.64283-2-nmi@metaspace.dk> <51b660f3-8145-d35e-87b4-d9ac0623606d@kernel.org> <87a5w3ymff.fsf@metaspace.dk> <875y6qzufc.fsf@metaspace.dk> User-agent: mu4e 1.10.4; emacs 28.2.50 From: "Andreas Hindborg (Samsung)" To: Christoph Hellwig Cc: 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 Date: Tue, 11 Jul 2023 12:15:18 +0200 In-reply-to: Message-ID: <871qhezr4d.fsf@metaspace.dk> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Christoph Hellwig writes: > On Tue, Jul 11, 2023 at 11:02:15AM +0200, Andreas Hindborg (Samsung) wrote: >> >> Christoph Hellwig writes: >> >> > 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. >> >> Both SCSI and NVMe has command identifier ranges reserved for vendor >> specific commands. I would assume that one use of these is to implement >> passthrough channels to a device for testing out new interfaces. Just >> guessing though. > > Vendor specific commands is an entirely different concept from Linux > passthrough requests. 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?