From: Matti Aarnio <matti.aarnio@zmailer.org>
To: "Roar Thronæs" <roart@nvg.ntnu.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: increase the number of system call parameters
Date: Mon, 22 Oct 2001 14:57:11 +0300 [thread overview]
Message-ID: <20011022145711.G24643@mea-ext.zmailer.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0110221334200.1121-100000@hagbart.nvg.ntnu.no>
In-Reply-To: <Pine.LNX.4.33.0110221334200.1121-100000@hagbart.nvg.ntnu.no>; from roart@nvg.ntnu.no on Mon, Oct 22, 2001 at 01:48:26PM +0200
On Mon, Oct 22, 2001 at 01:48:26PM +0200, Roar Thronæs wrote:
> Hi
>
> How do you increase the number of system call parameters, and how many
> can you at most have?
> Would up to 12 parameters be possible, and how?
Why ? Would it not make sense to have 2-3 params, one of them
being a pointer to a structure passing complicated dataset ?
(And first of the structure elements being version number so you
can version the syscall, e.g. add more things/differently structured
things latter -- and remember to supply specific errno which is
telling that particular version is not understood by the kernel.)
For example the kernel does not have mmap64(), but it has mmap2()
which passes the large number of parameters in a structure, and the
libc has a wrapper function implementing mmap64() call API.
At register-rich systems that is not absolutely necessary, but at
register-starved things, like i386, you have no real other way.
> --
> -Roar Thronæs
/Matti Aarnio
next prev parent reply other threads:[~2001-10-22 11:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-22 11:48 Roar Thronæs
2001-10-22 11:57 ` Matti Aarnio [this message]
2001-10-22 12:03 ` Andi Kleen
2001-10-22 21:37 ` Daniel Barlow
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=20011022145711.G24643@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roart@nvg.ntnu.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
all inboxes | Powered by JetHome®