Date: Sat, 3 Feb 2024 13:17:03 +0100 From: Robert Clausecker <fuz@freebsd.org> To: Mateusz Guzik <mjguzik@gmail.com> Cc: Brooks Davis <brooks@freebsd.org>, current@freebsd.org Subject: Re: libc/libsys split coming soon Message-ID: <Zb4uvxungi-EKsuL@fuz.su> In-Reply-To: <CAGudoHGoSW4Zwa9PT_O7AeQX%2B8Q9PKmoQBm9HrmdKD5PNfE0uw@mail.gmail.com> References: <Zb1tTz5LXuVQ5Caj@spindle.one-eyed-alien.net> <CAGudoHGoSW4Zwa9PT_O7AeQX%2B8Q9PKmoQBm9HrmdKD5PNfE0uw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Am Sat, Feb 03, 2024 at 10:15:09AM +0100 schrieb Mateusz Guzik: > Do I read it correctly that everything dynamically linked will also be > linked to libsys, as in executing such a binary will now require > loading one extra .so? > > Binary startup is very slow, for example execve of a hello world > binary in a Linux-based chroot on FreeBSD is faster by a factor of 2 > compared to a native one. As such perf-wise this looks like a step in > the wrong direction. I wonder if we could follow the steps of musl libc and just integrate libsys/libc into rtld, as basically all dynamically linked programs link these libraries anyway. Yours, Robert Clausecker -- () ascii ribbon campaign - for an encoding-agnostic world /\ - against html email - against proprietary attachments
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Zb4uvxungi-EKsuL>