From: john@csplan9.rit.edu
To: 9fans@9fans.net
Subject: Re: [9fans] two quick questions on syscalls
Date: Thu, 8 Jan 2009 12:22:02 -0500 [thread overview]
Message-ID: <2126e45d61538ffb0494c42977735f63@csplan9.rit.edu> (raw)
In-Reply-To: <1231434224.5141.229.camel@goose.sun.com>
> Hi!
>
> 1. are the ones starting from underscore totally deprecated?
> 2. what's the use for sysr1?
>
> Thanks,
> Roman.
To answer #2:
I found sysr1 useful while fiddling with devtrace, because it's a
syscall that does nothing. In addition to providing insights to how
long it takes to enter a syscall and return, it also gave me a place
to put in syscall things I wanted to test.
John
PS: I'm sitting in an engineering lab near a couple of shrill freshmen
arguing KDE vs. GNOME... apparently they just discovered Linux
because nobody has mentioned any other window manager in the whole 30
minutes.
next prev parent reply other threads:[~2009-01-08 17:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 17:03 Roman V. Shaposhnik
2009-01-08 17:22 ` john [this message]
2009-01-08 17:27 ` Russ Cox
2009-01-08 21:56 ` Pietro Gagliardi
2009-01-08 22:23 ` Charles Forsyth
2009-01-08 17:40 ` Charles Forsyth
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=2126e45d61538ffb0494c42977735f63@csplan9.rit.edu \
--to=john@csplan9.rit.edu \
--cc=9fans@9fans.net \
/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).