01-31-2012
When you make a function call, your program jumps to a different location in memory. It's just a program jump with a little extra stack work, nothing magic, just running around in its own private little universe (process).
To make a system call, you set registers to some particular values, call INT 0x20, and bang, it's done. Your own program doesn't jump anywhere or do anything -- the system call just happens, like magic, then leaves your program right where it started.
Code does execute, of course, but not in your program. INT 0x20 just passes a message into the operating system. When that happens, the OS literally stops your program, rearranges that program's private universe in the manner requested. Once it's finished, the kernel starts your program running again. This isn't necessarily instant. If you do a read() on a pipe or socket with no data in it, your program might be sleeping entire seconds for whatever's on the other end to write into it.
So. Function calls: Runs instructions inside your program. These instructions can't do anything except read or write memory or alter certain unprivileged registers.
System calls: Instantly stops your program and sends a message to the operating system, asking it to do something. The OS decides what to do with your request and does it, in kernel mode, with much higher privileges. Once finished, starts your program again.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
What does the system call "dup" do?
What is the difference between dup and dup2
I have a fair idea of what it does but I am confused when its coming down to the exact details...
Please help me!:confused: (2 Replies)
Discussion started by: clickonline1
2 Replies
2. UNIX for Dummies Questions & Answers
Which system calls are made for operations cp and mv (2 Replies)
Discussion started by: gaurava99
2 Replies
3. UNIX for Dummies Questions & Answers
open, creat, read, write, lseek and close
Are they all primitive?
:confused:
*Another Question: is there a different between a system call, and an i/o system call? (2 Replies)
Discussion started by: PlunderBunny
2 Replies
4. Solaris
where can i find the differences in System calls between solaris and aix?
also is it possible to find a comprehensive list of them? (1 Reply)
Discussion started by: TECHRAMESH
1 Replies
5. UNIX Desktop Questions & Answers
Hi,
I'm new to UNIX system calls. Can someone share your knowledge as to how exactly system calls should be executed?
Can they be typed like commands such as mkdir on the terminal itself? Also, are there any websites which will show me an example of the output to expect when a system call like... (1 Reply)
Discussion started by: ilavenil
1 Replies
6. Programming
why user is not able to switch from user to kernel mode by writing the function whose code is identical to system call. (1 Reply)
Discussion started by: joshighanshyam
1 Replies
7. BSD
what is the functions and relationship between fork,exec,wait system calls
as i am a beginer just want the fundamentals. (1 Reply)
Discussion started by: sangramdas
1 Replies
8. Programming
#include<unistd.h>
#include<sys/types.h>
#include<sys/stat.h>
#include<fcntl.h>
#include<stdlib.h>
int main( int argc,char *argv )
{
char buf;
int sourcefile,destfile,n;
if(argc!=3)
{
write(STDOUT_FILENO,"prgm1 <sourcefile> <destination file>\n",50);
... (6 Replies)
Discussion started by: c_d
6 Replies
9. UNIX for Dummies Questions & Answers
Hi all,
I am new here .
I want to know about system call in detail.
As system calls are also function .How system identifies it.:) (2 Replies)
Discussion started by: vishwasrao
2 Replies
10. UNIX for Dummies Questions & Answers
I'm currently studying for my exam, and is practicing with sample exam questions.
However there is a question asking "Name THREE UNIX Directory system calls" and the answer given is "opendir, closedir and readdir", however the next question ask "Why is a write directory system call not included... (1 Reply)
Discussion started by: Izzy123
1 Replies
LEARN ABOUT DEBIAN
getpgid
GETPGRP(2) BSD System Calls Manual GETPGRP(2)
NAME
getpgrp -- get process group
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <unistd.h>
pid_t
getpgrp(void);
pid_t
getpgid(pid_t pid);
DESCRIPTION
The process group of the current process is returned by getpgrp(). The process group of the process identified by pid is returned by
getpgid(). If pid is zero, getpgid() returns the process group of the current process.
Process groups are used for distribution of signals, and by terminals to arbitrate requests for their input: processes that have the same
process group as the terminal are foreground and may read, while others will block with a signal if they attempt to read.
This system call is thus used by programs such as csh(1) to create process groups in implementing job control. The tcgetpgrp() and
tcsetpgrp() calls are used to get/set the process group of the control terminal.
RETURN VALUES
The getpgrp() system call always succeeds. Upon successful completion, the getpgid() system call returns the process group of the specified
process; otherwise, it returns a value of -1 and sets errno to indicate the error.
COMPATIBILITY
This version of getpgrp() differs from past Berkeley versions by not taking a pid_t pid argument. This incompatibility is required by
ISO/IEC 9945-1:1990 (``POSIX.1'').
From the ISO/IEC 9945-1:1990 (``POSIX.1'') Rationale:
4.3BSD provides a getpgrp() system call that returns the process group ID for a specified process. Although this function is used to support
job control, all known job-control shells always specify the calling process with this function. Thus, the simpler AT&T System V UNIX
getpgrp() suffices, and the added complexity of the 4.3BSD getpgrp() has been omitted from POSIX.1. The old functionality is available from
the getpgid() system call.
ERRORS
The getpgid() system call will succeed unless:
[ESRCH] there is no process whose process ID equals pid
SEE ALSO
getsid(2), setpgid(2), termios(4)
STANDARDS
The getpgrp() system call is expected to conform to ISO/IEC 9945-1:1990 (``POSIX.1'').
HISTORY
The getpgrp() system call appeared in 4.0BSD. The getpgid() system call is derived from its usage in AT&T System V Release 4 UNIX.
BSD
June 4, 1993 BSD