From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-x42a.google.com (mail-wr1-x42a.google.com [IPv6:2a00:1450:4864:20::42a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 1670D3B29D for ; Thu, 13 Oct 2022 16:04:34 -0400 (EDT) Received: by mail-wr1-x42a.google.com with SMTP id bp11so4490633wrb.9 for ; Thu, 13 Oct 2022 13:04:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=Lk76OD76kMomfiIZ29izNwOyva4xKlAWxVSq5HdlWq0=; b=SOqX0G4zcjEfcFeTsWZvHqdVNGhuhg0p6kxZVNfnzBCOQOjltL2vZy6bTALZj5b0Qp A4uvwdxbtd9gTTEgdSeovPTR3u+8VFeZAL6gRVLGUWwBZsaaCVIRdfNpLW4ALDTuZBKG hMTJZ72OZht/VpGjC5QkBquLxFp80eMST19jStjqi0TDqyDmE2r+hK4UNS9ZkT3WLfUW rcwerpPjaKnHQYtEhQ21+bi/i8eAFCxdUOjBpGcJEQvn8/WQ1wVPv9cR33aPE7eZPJhP t42tA6GPW+K0lKeLsVI3XZHcdbGKUk6u8u0g49uG0tIAT3bZB2/jmfEgylyr08Eeua9e 4JIg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=Lk76OD76kMomfiIZ29izNwOyva4xKlAWxVSq5HdlWq0=; b=gUKbZOWJOBTBjJggV85nJMeXppuHYL4mAaPibEUWi7jzyB8IZA0gF52BdRpUBajSfW EBXfYZj9uAnLqrTUw+gmR2uP+z4B/fXlYsLPQ52vBPXc2zMQzohLbOK+R0L3NrSoIOFN va5fxXLIX+sv3PhMLMAuCMANQN/ZzDI1UAFaOmRvZ+YxIqTEgjVCvzXkiAbNfZOmPxpf vnVjpcmS4U+BcM4U9JEa38ZpbskWsTiWFi+XkYWQWX0atP7LvWOyAZN2AHYGVYX2OfRE v+3RKc64yWFKeze9VNP3lPvexpSfrVeDtAYe/77uTx26ovqd5hbvQYpQykC0hV1V0H0P WIZQ== X-Gm-Message-State: ACrzQf0hmG6tVKICVzgd2vWsTqwSeq1sbnKyFYhM2now47PTmp6kDRpQ 7t0lIp7mxnKrzDMTDKWYi0y0v+JdLT0M1ilRCCbFuC9r X-Google-Smtp-Source: AMsMyM70cByYF0G+A7y9GZqPB+ixUS+Qit1iEBuuHbvbs42+Oq4hWua4LGXrj2LahhAolDsRDmYAs9NhYqj79xlvulw= X-Received: by 2002:a5d:5109:0:b0:22f:ed4:65da with SMTP id s9-20020a5d5109000000b0022f0ed465damr1037241wrt.688.1665691472326; Thu, 13 Oct 2022 13:04:32 -0700 (PDT) MIME-Version: 1.0 References: <20220930023418.1346263-1-kuba@kernel.org> In-Reply-To: <20220930023418.1346263-1-kuba@kernel.org> From: Dave Taht Date: Thu, 13 Oct 2022 13:04:17 -0700 Message-ID: To: libreqos@lists.bufferbloat.net, Jakub Kicinski Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: [LibreQoS] Fwd: [PATCH net-next v2 0/7] Netlink protocol specs X-BeenThere: libreqos@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Oct 2022 20:04:34 -0000 I am told 3+ people are trying to turn the yaml netlink spec into rust. It would be good to co-ordinate and leverage their work for libreqos.io but I don't know who or where they are doing that work. ---------- Forwarded message --------- From: Jakub Kicinski Date: Thu, Sep 29, 2022 at 7:37 PM Subject: [PATCH net-next v2 0/7] Netlink protocol specs To: Cc: , , , , , , , , , , , , , , Jakub Kicinski Hi! I think the Netlink proto specs are far along enough to merge. Filling in all attribute types and quirks will be an ongoing effort but we have enough to cover FOU so it's somewhat complete. I fully intend to continue polishing the code but at the same time I'd like to start helping others base their work on the specs (e.g. DPLL) and need to start working on some new families myself. That's the progress / motivation for merging. The RFC [1] has more of a high level blurb, plus I created a lot of documentation, I'm not going to repeat it here. There was also the talk at LPC [2]. [1] https://lore.kernel.org/all/20220811022304.583300-1-kuba@kernel.org/ [2] https://youtu.be/9QkXIQXkaQk?t=3D2562 v2: - update docs - change comment format in uAPI from // to /* */ - rename fou.c to make linker happy Jakub Kicinski (7): docs: add more netlink docs (incl. spec docs) netlink: add schemas for YAML specs net: add basic C code generators for Netlink netlink: add a proto specification for FOU net: fou: regenerate the uAPI from the spec net: fou: rename the source for linking net: fou: use policy and operation tables generated from the spec Documentation/core-api/index.rst | 1 + Documentation/core-api/netlink.rst | 99 + Documentation/netlink/genetlink-c.yaml | 287 +++ Documentation/netlink/genetlink-legacy.yaml | 313 +++ Documentation/netlink/genetlink.yaml | 252 +++ Documentation/netlink/specs/fou.yaml | 128 ++ .../userspace-api/netlink/c-code-gen.rst | 104 + .../netlink/genetlink-legacy.rst | 96 + Documentation/userspace-api/netlink/index.rst | 5 + Documentation/userspace-api/netlink/specs.rst | 410 ++++ MAINTAINERS | 3 + include/uapi/linux/fou.h | 54 +- net/ipv4/Makefile | 1 + net/ipv4/fou-nl.c | 48 + net/ipv4/fou-nl.h | 25 + net/ipv4/{fou.c =3D> fou_core.c} | 51 +- tools/net/ynl/ynl-gen-c.py | 1998 +++++++++++++++++ tools/net/ynl/ynl-regen.sh | 30 + 18 files changed, 3835 insertions(+), 70 deletions(-) create mode 100644 Documentation/core-api/netlink.rst create mode 100644 Documentation/netlink/genetlink-c.yaml create mode 100644 Documentation/netlink/genetlink-legacy.yaml create mode 100644 Documentation/netlink/genetlink.yaml create mode 100644 Documentation/netlink/specs/fou.yaml create mode 100644 Documentation/userspace-api/netlink/c-code-gen.rst create mode 100644 Documentation/userspace-api/netlink/genetlink-legacy.rs= t create mode 100644 Documentation/userspace-api/netlink/specs.rst create mode 100644 net/ipv4/fou-nl.c create mode 100644 net/ipv4/fou-nl.h rename net/ipv4/{fou.c =3D> fou_core.c} (94%) create mode 100755 tools/net/ynl/ynl-gen-c.py create mode 100755 tools/net/ynl/ynl-regen.sh -- 2.37.3 --=20 This song goes out to all the folk that thought Stadia would work: https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-69813666656= 07352320-FXtz Dave T=C3=A4ht CEO, TekLibre, LLC