From: "Joshua M. Clulow via illumos-discuss" <discuss@lists.illumos.org>
To: illumos-discuss <discuss@lists.illumos.org>
Subject: Re: [discuss] whats the /lib/libc.so.1 mount for ?
Date: Fri, 31 Jan 2025 14:18:54 -0800 [thread overview]
Message-ID: <CAEwA5nLyZCi8XZqNnW+y6JZ9Rytr8-c9OgdK4zLUS5zct2j1zQ@mail.gmail.com> (raw)
In-Reply-To: <SJ2PR20MB71556A21D23361EEF7289D22A4E82@SJ2PR20MB7155.namprd20.prod.outlook.com>
On Fri, 31 Jan 2025 at 09:09, Jason King <jason.brian.king@gmail.com> wrote:
> Newer libraries would likely use linker capabilities to do this in a single library (if the author is aware of them – it’s actually a neat feature that isn’t as well known as it should be IMO). I don’t have access to the relevant history (this all predates illumos), but my best guess is that the linker functionality to allow selection of an optimized implementation of a function based on CPU capabilities probably came later (and no one’s been interested in doing the work to consolidate them – I suspect it’d get rather tedious).
I think it also depends on how much of the program text ends up having
to change. In the libc case, though I have not looked at this moment,
it's conceivable that there are a lot of syscall stubs laced
throughout the program text. A whole-library switch may facilitate
better sharing of pages, or might just be faster to link, etc. It
would require some investigation and measurement to know one way or
another.
Cheers.
--
Joshua M. Clulow
http://blog.sysmgr.org
------------------------------------------
illumos: illumos-discuss
Permalink: https://illumos.topicbox.com/groups/discuss/T9811b44617503fdd-M55052f5a732b87ae7a528ffd
Delivery options: https://illumos.topicbox.com/groups/discuss/subscription
prev parent reply other threads:[~2025-01-31 22:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 16:43 Enrico Weigelt, metux IT consult
2025-01-31 16:45 ` Udo Grabowski (IMKASF)
2025-01-31 16:55 ` Udo Grabowski (IMKASF)
2025-01-31 17:09 ` Jason King
2025-01-31 22:18 ` Joshua M. Clulow via illumos-discuss [this message]
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=CAEwA5nLyZCi8XZqNnW+y6JZ9Rytr8-c9OgdK4zLUS5zct2j1zQ@mail.gmail.com \
--to=discuss@lists.illumos.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).