From: Frank Schaefer <frank.schafer@setuza.cz>
To: linux-kernel@vger.kernel.org
Subject: Re: syscals
Date: 09 Apr 2002 12:06:30 +0200 [thread overview]
Message-ID: <1018346790.680.10.camel@ADMIN> (raw)
In-Reply-To: <20020409021047.518A53ECC@sitemail.everyone.net>
On Tue, 2002-04-09 at 04:10, mark manning wrote:
> ok - according to unistd.h we now have exactly 256 syscalls allocated (unless im missing something). my code needs to be able to account for every single possible syscall and so i need to be able to store the syscall number in a standard way. not all syscalls are catered for on the outset by at any time the user can say "i need to use syscall x which takes y parameters" and the code will be able to take care of it.
>
> the problem is that i am currently reserving only 8 bits for the syscall number. this is ok for now but if we ever get another syscall its going to be unuseable by my existing code :) - should i be reserving 16 bits now in preperation for some new syscalls being added ?
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
Hmm...
dunno if you got this right. There are maximal 256 syscalls possible,
and, right -- exactly this amount of syscalls is in the entrytable. But
alotalotalot of them are defined as sys_ni_syscall (not yet
implemented).
I think there is still some space for enhancements. See
arch/i386/kernel/entry.S.
Regards
Frank
next prev parent reply other threads:[~2002-04-09 10:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-09 2:10 syscals mark manning
2002-04-09 10:06 ` Frank Schaefer [this message]
2002-04-09 10:19 ` Compaq Alpha DS10 - Kernel 2.4.18 Oliver Pitzeier
2002-04-09 11:25 ` Damian Wrobel
2002-04-09 12:16 ` dr john halewood
2002-04-09 15:09 ` syscals Randy.Dunlap
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=1018346790.680.10.camel@ADMIN \
--to=frank.schafer@setuza.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.