From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: common name for the kernel DSO
Date: 18 Jun 2003 23:18:02 -0700 [thread overview]
Message-ID: <bcrkiq$dta$1@cesium.transmeta.com> (raw)
In-Reply-To: 16112.47509.643668.116939@napali.hpl.hp.com
Followup to: <16112.47509.643668.116939@napali.hpl.hp.com>
By author: David Mosberger <davidm@napali.hpl.hp.com>
In newsgroup: linux.dev.kernel
>
> Both x86 and ia64 now provide a dynamically shared object (DSO) for
> system call purposes (e.g., to speed up system calls and for signal
> trampoline/sigreturn purposes). At the moment, the names of these
> DSOs are different:
>
> x86: linux-vsyscall.so.1
> ia64: linux-gate.so.1
>
> I think there is some value in using the same name on all platforms
> that support such a DSO. vsyscall makes no sense for ia64, since
> there are no virtual syscalls (instead, ia64 linux provides a fast
> system call convention which, when coupled with light-weight system
> call handlers, provide full syscall semantics at more or less the
> speed of virtual system calls).
>
> Not surprisingly, I like the name "linux-gate", since that is really
> what this DSO is all about: it's a gateway between user and kernel
> space. However, if this name isn't appropriate for x86, perhaps we
> can find another name which will be acceptable to everybody.
>
It's a pretty ugly name, quite frankly, since it doesn't explain what
it is a gate from or to. linux-syscall.so.1 or linux-kernel.so.1
would make a lot more sense.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
next prev parent reply other threads:[~2003-06-19 6:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-18 19:12 common name for the kernel DSO David Mosberger
2003-06-18 20:32 ` Sam Ravnborg
2003-06-18 20:35 ` David Mosberger
2003-06-18 22:51 ` David Mosberger
2003-06-18 23:35 ` Andrew Morton
2003-06-18 23:56 ` David Mosberger
2003-06-25 3:19 ` Roland McGrath
2003-06-19 6:18 ` H. Peter Anvin [this message]
2003-06-19 6:25 ` David Mosberger
2003-06-19 6:46 ` H. Peter Anvin
2003-06-19 6:49 ` David Mosberger
2003-06-21 6:42 ` Pavel Machek
2003-06-19 19:15 ` Jamie Lokier
[not found] <20030618192007$14a5@gated-at.bofh.it>
[not found] ` <20030619062011$555e@gated-at.bofh.it>
[not found] ` <20030619192018$5cab@gated-at.bofh.it>
2003-06-19 20:26 ` David Mosberger-Tang
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='bcrkiq$dta$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.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