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 4FCD9C433EF for ; Thu, 9 Jun 2022 22:03:04 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234578AbiFIWDC (ORCPT ); Thu, 9 Jun 2022 18:03:02 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33134 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229950AbiFIWDB (ORCPT ); Thu, 9 Jun 2022 18:03:01 -0400 Received: from a3.inai.de (a3.inai.de [IPv6:2a01:4f8:10b:45d8::f5]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8B771196A99; Thu, 9 Jun 2022 15:02:59 -0700 (PDT) Received: by a3.inai.de (Postfix, from userid 25121) id EFA0A58723354; Fri, 10 Jun 2022 00:02:56 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by a3.inai.de (Postfix) with ESMTP id ECAB160C247C3; Fri, 10 Jun 2022 00:02:56 +0200 (CEST) Date: Fri, 10 Jun 2022 00:02:56 +0200 (CEST) From: Jan Engelhardt To: Kent Overstreet cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, linux-block@vger.kernel.org, netdev@vger.kernel.org, mcgrof@kernel.org, tytso@mit.edu Subject: Re: RFC: Ioctl v2 In-Reply-To: <20220520161652.rmhqlvwvfrvskg4w@moria.home.lan> Message-ID: <6s1p436o-r4ss-p9n0-o486-qo7s747n6913@vanv.qr> References: <20220520161652.rmhqlvwvfrvskg4w@moria.home.lan> User-Agent: Alpine 2.25 (LSU 592 2021-09-18) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Friday 2022-05-20 18:16, Kent Overstreet wrote: >Problems with ioctls: > >* There's no namespacing, and ioctl numbers clash > >IOCTL v2 proposal: > >* Namespacing > >To solve the namespacing issue, I want to steal an approach I've seen from >OpenGL, where extensions are namespaced: an extension will be referenced by name >where the name is vendor.foo, and when an extension becomes standard it gets a >new name (arb.foo instead of nvidia.foo, I think? it's been awhile). >To do this we'll need to define ioctls by name, not by hardcoded number, [...] https://www.khronos.org/registry/vulkan/specs/1.3-extensions/man/html/VK_NV_glsl_shader.html Right there on the front matter: "Registered number #13". https://www.khronos.org/registry/vulkan/specs/1.3/styleguide.html "All extensions must be registered with Khronos." "Each extension is assigned a range of values that can be used to create globally-unique enum values"