9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "rob pike, esq." <rob@mightycheese.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Looking for namespace details
Date: Sat,  8 Feb 2003 09:17:39 -0800	[thread overview]
Message-ID: <2d2de0c7a2cec61d339f6863c37f2cd2@mightycheese.com> (raw)
In-Reply-To: <3E45339D.7070008@bar.net>

> My question is -- where is the code for the kernel side of these calls?

Some of the system calls are wrapped in libc first - for example,
read() is a wrapper for pread() - but on average, system call foo is
connected by a trap through a table defined in
/sys/src/9/port/systab.h (generated automatically from
/sys/src/libc/9syscall/sys.h) to a routine in /sys/src/9/port/sys*.c
called sysfoo().  A few later system calls appear in files not
beginning with "sys", a regrettable lapse.

-rob



  parent reply	other threads:[~2003-02-08 17:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-08 16:43 Glenn McGuire
2003-02-08 16:46 ` Dan Cross
2003-02-08 16:46 ` Russ Cox
2003-02-08 17:17 ` rob pike, esq. [this message]
2003-02-10  8:32 ` Fco.J.Ballesteros
2003-02-13  0:30   ` Glenn McGuire
2003-02-08 16:45 David Presotto

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=2d2de0c7a2cec61d339f6863c37f2cd2@mightycheese.com \
    --to=rob@mightycheese.com \
    --cc=9fans@cse.psu.edu \
    /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;
as well as URLs for NNTP newsgroup(s).