From: Robert Love <rml@novell.com>
To: Rodrigo Ramos <rodrigo.ramos@triforsec.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: system calls
Date: Sat, 29 Jan 2005 12:47:38 -0500 [thread overview]
Message-ID: <1107020858.11159.15.camel@localhost> (raw)
In-Reply-To: <1107006832.2732.35.camel@ZeroOne>
On Sat, 2005-01-29 at 10:53 -0300, Rodrigo Ramos wrote:
> I would like to know how many groups of system calls are there at Linux
> 2.4 and 2.6? Where can I find these informations in the Kernel?
I don't know what you mean by groups (a nonempty set G with binary
operation * s.t. G is associativity, there exists e in G s.t. e*a=a*e=a,
and there exists i in G s.t. i*b=b*i=e?).
System calls are implemented per-architecture. You can see the list at
the bottom of arch/i386/kernel/entry.S. There is about 290.
System calls are prefixed by "sys_". Thus, read(2) is implemented in
the kernel as sys_read(). It, for example, can be found in
fs/read_write.c.
Hope this helps.
Robert Love
next prev parent reply other threads:[~2005-01-29 17:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-29 13:53 system calls Rodrigo Ramos
2005-01-29 17:47 ` Robert Love [this message]
2005-01-29 18:15 ` Andries Brouwer
2005-01-31 12:04 ` Rodrigo Ramos
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=1107020858.11159.15.camel@localhost \
--to=rml@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.ramos@triforsec.com.br \
/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