From: Ralf Baechle <ralf@uni-koblenz.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Terje Eggestad <terje.eggestad@scali.com>,
Amber Palekar <amber_palekar@yahoo.com>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Again:syscall from modules
Date: Fri, 28 Dec 2001 13:41:06 -0200 [thread overview]
Message-ID: <20011228134106.B1323@dea.linux-mips.net> (raw)
In-Reply-To: <20011225131441.60811.qmail@web20306.mail.yahoo.com> <1009468465.15846.0.camel@eggis1> <15403.28458.153083.961800@charged.uio.no>
In-Reply-To: <15403.28458.153083.961800@charged.uio.no>; from trond.myklebust@fys.uio.no on Thu, Dec 27, 2001 at 07:57:46PM +0100
On Thu, Dec 27, 2001 at 07:57:46PM +0100, Trond Myklebust wrote:
> You are scaremongering a bit here. Several of the sys_* functions
> *are* generic, and could be called by quite safely by the kernel. Look
> for instance at the use of sys_close() by the binfmt stuff.
>
> Normally, though, there will be a price to pay in terms of an
> overhead.
> Furthermore, if you find that you absolutely *have* to use the sys_*
> interface, from userspace you will probably want to rethink your
> design: after all you can call all those sys_* functions from user
> space, and the rule of thumb is that if you *can* do something in user
> space, you ought to do it there...
Many sys_*() functions may be in the generic code but that still doesn't
mean the ports are actually using it or that no special calling sequence
which normally would be done in libc is required. Only people doing
syscalls themselfes and not through libc wrappers is worse ...
Ralf
next prev parent reply other threads:[~2001-12-28 15:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-25 11:31 syscall from modules Amber Palekar
2001-12-25 13:09 ` Trond Myklebust
2001-12-25 13:14 ` Again:syscall " Amber Palekar
2001-12-25 18:37 ` Trond Myklebust
2001-12-27 15:54 ` Terje Eggestad
2001-12-27 16:04 ` Terje Eggestad
2001-12-27 18:57 ` Trond Myklebust
2001-12-28 15:41 ` Ralf Baechle [this message]
2001-12-28 15:48 ` Trond Myklebust
2001-12-28 16:26 ` Ralf Baechle
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=20011228134106.B1323@dea.linux-mips.net \
--to=ralf@uni-koblenz.de \
--cc=amber_palekar@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=terje.eggestad@scali.com \
--cc=trond.myklebust@fys.uio.no \
/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