Date: Fri, 22 Aug 2025 21:48:48 +0300 From: Vadim Goncharov <vadimnuclight@gmail.com> To: David Chisnall <theraven@FreeBSD.org> Cc: Poul-Henning Kamp <phk@phk.freebsd.dk>, Konstantin Belousov <kostikbel@gmail.com>, hackers@freebsd.org Subject: Re: My experiences with Rust Message-ID: <20250822214848.25569826@nuclight.lan> In-Reply-To: <E04D6E14-8EA1-446B-8C9C-762C9956F6D5@FreeBSD.org> References: <aKiWZ1I3pqZSOsfk@kib.kiev.ua> <202508221712.57MHCPDl008201@critter.freebsd.dk> <E04D6E14-8EA1-446B-8C9C-762C9956F6D5@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
On Fri, 22 Aug 2025 18:26:45 +0100
David Chisnall <theraven@FreeBSD.org> wrote:
> On 22 Aug 2025, at 18:12, Poul-Henning Kamp <phk@phk.freebsd.dk> wrote:
> >
> > Aka: the guy who added kern.geom.confxml in 2002
>
> XML is not great for generating or parsing, but we have nvlist
> infrastructure in the kernel and a nice library (and a less-nice library
> that you have to use if you link libzfs{core}) in base. I would love to see
> more interfaces to the kernel switch to using nvlists. They should be the
> default for *any* new kernel interface that isn’t 100% performance critical.
> Certainly any system-reporting or control-plane interfaces should be using
> nvlists.
Why it should be reinvented-wheel-bicycle "nvlist" instead of CBOR, RFC 8949,
Internet Standard 94 ? It's forgivable that nvlists are used in ZFS code, as
nothing better existed two decades ago (just as with XML at same times, not
even JSON), but that should be strictly confined to Solaris port and not be
used anywhere else, not even to mention security vulnerabilities.
BTW, libxo even has some CBOR code inside.
--
WBR, @nuclight
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20250822214848.25569826>