From: Jakub Kicinski <kuba@kernel•org>
To: Alexander Aring <aahringo@redhat•com>
Cc: teigland@redhat•com, gfs2@lists•linux.dev, song@kernel•org,
yukuai3@huawei•com, agruenba@redhat•com, mark@fasheh•com,
jlbec@evilplan•org, joseph.qi@linux•alibaba.com,
gregkh@linuxfoundation•org, rafael@kernel•org,
akpm@linux-foundation•org, linux-kernel@vger•kernel.org,
linux-raid@vger•kernel.org, ocfs2-devel@lists•linux.dev,
netdev@vger•kernel.org, vvidic@valentin-vidic•from.hr,
heming.zhao@suse•com, lucien.xin@gmail•com
Subject: Re: [PATCH dlm/next 11/12] dlm: add nldlm net-namespace aware UAPI
Date: Wed, 21 Aug 2024 15:57:36 -0700 [thread overview]
Message-ID: <20240821155736.64d0350c@kernel.org> (raw)
In-Reply-To: <CAK-6q+hx8MNeZCc0T-sTPdMgXH=ZcpLVqc2-5+psMCoQ_W0FxA@mail.gmail.com>
On Wed, 21 Aug 2024 09:13:21 -0400 Alexander Aring wrote:
> > Did you consider using the YAML spec stuff to code gen the policies
> > and make user space easier?
>
> I will try to take a look into that and prepare a spec for PATCHv2. I
> saw that there is a documentation about it at [0].
>
> I did a kind of "prototype" libnldlm [1] to have easy access to the
> netlink api but if there are more common ways to generate code to
> easily access it, I am happy to give it a try.
Right, even if you don't end up using it on the user space side, having
YNL generate the kernel boiler plate simplifies the human review, if
nothing else :) YNL always uses the latest and safest kernel constructs.
next prev parent reply other threads:[~2024-08-21 22:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 18:37 [PATCH dlm/next 00/12] dlm: net-namespace functionality Alexander Aring
2024-08-19 18:37 ` [PATCH dlm/next 01/12] dlm: introduce dlm_find_lockspace_name() Alexander Aring
2024-08-19 18:37 ` [PATCH dlm/next 02/12] dlm: disallow different configs nodeid storages Alexander Aring
2024-08-19 18:37 ` [PATCH dlm/next 03/12] dlm: add struct net to dlm_new_lockspace() Alexander Aring
2024-08-19 18:37 ` [PATCH dlm/next 04/12] dlm: handle port as __be16 network byte order Alexander Aring
2024-08-19 18:37 ` [PATCH dlm/next 05/12] dlm: use dlm_config as only cluster configuration Alexander Aring
2024-08-19 18:37 ` [PATCH dlm/next 06/12] dlm: dlm_config_info config fields to unsigned int Alexander Aring
2024-08-19 18:37 ` [PATCH dlm/next 07/12] dlm: rename config to configfs Alexander Aring
2024-08-19 18:37 ` [PATCH dlm/next 08/12] kobject: add kset_type_create_and_add() helper Alexander Aring
2024-08-19 18:37 ` [PATCH dlm/next 09/12] kobject: export generic helper ops Alexander Aring
2024-08-19 18:37 ` [PATCH dlm/next 10/12] dlm: separate dlm lockspaces per net-namespace Alexander Aring
2024-08-20 19:22 ` Dan Carpenter
2024-08-19 18:37 ` [PATCH dlm/next 11/12] dlm: add nldlm net-namespace aware UAPI Alexander Aring
2024-08-19 22:12 ` Jakub Kicinski
2024-08-21 13:13 ` Alexander Aring
2024-08-21 22:57 ` Jakub Kicinski [this message]
2024-08-20 7:40 ` kernel test robot
2024-08-19 18:37 ` [PATCH dlm/next 12/12] gfs2: separate mount context by net-namespaces Alexander Aring
2024-08-20 14:42 ` kernel test robot
2024-08-20 17:37 ` kernel test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240821155736.64d0350c@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=aahringo@redhat$(echo .)com \
--cc=agruenba@redhat$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=gfs2@lists$(echo .)linux.dev \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=heming.zhao@suse$(echo .)com \
--cc=jlbec@evilplan$(echo .)org \
--cc=joseph.qi@linux$(echo .)alibaba.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-raid@vger$(echo .)kernel.org \
--cc=lucien.xin@gmail$(echo .)com \
--cc=mark@fasheh$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=ocfs2-devel@lists$(echo .)linux.dev \
--cc=rafael@kernel$(echo .)org \
--cc=song@kernel$(echo .)org \
--cc=teigland@redhat$(echo .)com \
--cc=vvidic@valentin-vidic$(echo .)from.hr \
--cc=yukuai3@huawei$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox