From: Bernd Petrovitsch <bernd@firmix.at>
To: walking.to.remember@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: what will connect the fork() with its following code ? a simple example below:
Date: Tue, 06 Sep 2005 12:37:55 +0200 [thread overview]
Message-ID: <1126003076.31664.5.camel@tara.firmix.at> (raw)
In-Reply-To: <6b5347dc0509060215128d477e@mail.gmail.com>
On Tue, 2005-09-06 at 17:15 +0800, Sat. wrote:
> if(!(pid=fork())){
> ......
> printk("in child process");
> ......
> }else{
> .....
> printk("in father process");
> .....
> }
>
> this is a classical example, when the fork() system call runs, it will
> build a new process and active it . while the schedule() select the
> new process it will run. this is rather normal.
>
> but there is always a confusion in my minds.
> because , sys_fork() only copies father process and configure some new
> values., and do nothing . so the bridge between the new process and
> its following code, printk("in child process"), seems disappear . so I
No, it is the same point as in the parent process - just the fork()
call. In fact the fork() returns twice - once within the parent process
(returning as result the pid of the child) and once within the child
(returning 0) [ and we ignore the error case for simplicity ].
Basically you are not forced to do a if() or switch() on the return
value(s) of fork()
---- snip ----
printf("1. fork() in process %d returned %d\n", getpid(), fork());
printf("2. fork() in process %d returned %d\n", getpid(), fork());
printf("3. fork() in process %d returned %d\n", getpid(), fork());
printf("4. fork() in process %d returned %d\n", getpid(), fork());
printf("5. fork() in process %d returned %d\n", getpid(), fork());
---- snip ----
Put this in a main() function and try it out.
> always believe that the new process should have a pointer which point
> the code "printk("in child process");". except this , there are not
> any connection between them ?
The kernel doesn't know (or care) about the C code (e.g. if(), ...) in
your application.
The "pointer" (if you want to call it) is the normal instruction pointer
(or what else it is called on your CPU).
> very confused :(
Bernd
--
Firmix Software GmbH http://www.firmix.at/
mobil: +43 664 4416156 fax: +43 1 7890849-55
Embedded Linux Development and Services
next prev parent reply other threads:[~2005-09-06 10:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-06 9:15 what will connect the fork() with its following code ? a simple example below: Sat.
2005-09-06 10:37 ` Bernd Petrovitsch [this message]
[not found] ` <003a01c5b2d6$610d6360$6464a8c0@pc0001>
2005-09-06 11:59 ` Sat.
2005-09-06 12:41 ` linux-os (Dick Johnson)
2005-09-06 13:01 ` Dirk Gerdes
2005-09-06 16:58 ` Valdis.Kletnieks
2005-09-07 7:08 ` Bernd Petrovitsch
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=1126003076.31664.5.camel@tara.firmix.at \
--to=bernd@firmix.at \
--cc=linux-kernel@vger.kernel.org \
--cc=walking.to.remember@gmail.com \
/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