From: hpa@zytor.com (H. Peter Anvin)
To: linux-kernel@vger.kernel.org
Subject: Re: [RFC] dynamic syscalls revisited
Date: Mon, 6 Dec 2004 21:14:25 +0000 (UTC) [thread overview]
Message-ID: <cp2i3h$hs0$1@terminus.zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0411291740390.30846@yvahk01.tjqt.qr>
Followup to: <Pine.LNX.4.53.0411291740390.30846@yvahk01.tjqt.qr>
By author: Jan Engelhardt <jengelh@linux01.gwdg.de>
In newsgroup: linux.dev.kernel
>
> I do not see how dsyscalls could be better than static ones, so they are
> one-on-one. Maybe someone could elaborate why they are "a really bad idea"?
>
Because we already have a name resolution mechanism in the kernel,
called the filesystem? We also have a mechanism for ad hoc system
calls, it's called ioctl().
And before you go "but ioctl() sucks": dynamic syscalls suck for
*exactly* the same reasons.
-hpa
next prev parent reply other threads:[~2004-12-06 21:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 15:11 [PATCH][RFC] " Steven Rostedt
2004-11-29 15:17 ` Christoph Hellwig
2004-11-29 15:36 ` Steven Rostedt
2004-11-30 19:30 ` Kristian Sørensen
2004-11-29 16:41 ` [RFC] " Jan Engelhardt
2004-11-29 17:10 ` Steven Rostedt
2004-12-05 23:46 ` Adrian Bunk
2004-12-06 16:07 ` Steven Rostedt
2004-12-06 17:16 ` Steven Rostedt
2004-12-06 17:32 ` Zwane Mwaikambo
2004-12-06 17:57 ` linux-os
2004-12-06 18:03 ` Steven Rostedt
2004-12-06 18:18 ` Arjan van de Ven
2004-12-07 0:20 ` Michael Buesch
2004-12-07 0:57 ` Steven Rostedt
2004-12-06 21:14 ` H. Peter Anvin [this message]
2004-12-06 22:01 ` Steven Rostedt
2004-12-06 22:20 ` H. Peter Anvin
2004-12-06 22:38 ` Steven Rostedt
2004-12-14 23:14 ` Werner Almesberger
2004-12-15 2:14 ` Steven Rostedt
2004-12-15 3:35 ` Steven Rostedt
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='cp2i3h$hs0$1@terminus.zytor.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
Powered by JetHome