From: "Arun Srinivas" <getarunsri@hotmail.com>
To: rostedt@goodmis.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: scheduler/SCHED_FIFO behaviour
Date: Mon, 02 May 2005 10:57:29 +0530 [thread overview]
Message-ID: <BAY10-F2709F2A16EEE74732F797FD9270@phx.gbl> (raw)
In-Reply-To: <1114962685.5081.5.camel@localhost.localdomain>
The 2 processes which I am measuring are parent and child processes.I want
both of'em to be scheduled at the same time.My code simply does the
following:
1) From main(i.e., parent) create a shared memory seg. using shmget() and
shmat(). This is for communication between parent and child. I am trying to
use this as a locking mechanism to make them tightly coupled so that one
does not race before the other.
2) create child by fork() and call shmat() to attach this segment to child
too
3) In parent and child call ioctl() to pass their PID's from user space to
kernel space...so that I can measure when the particular PID's are scheduled
in the scheduler
I suppose shmget() dosent use a system call.So still confused about the
occasional resechedule behavior.
>From: Steven Rostedt <rostedt@goodmis.org>
>To: Arun Srinivas <getarunsri@hotmail.com>
>CC: linux-kernel@vger.kernel.org
>Subject: Re: scheduler/SCHED_FIFO behaviour
>Date: Sun, 01 May 2005 11:51:25 -0400
>
>On Sun, 2005-05-01 at 07:36 +0530, Arun Srinivas wrote:
> > hi
> >
> > I spkoe to you some days ago regarding scheduling two processes
>together
> > on a HT.As I told you before I run them as SCHED_FIFO processes.I
>understood
> > the theory you told me in your previous reply as to why both of
>SCHED_FIFO
> > processes get scheduled only once and then run till completion.
> >
> > But, sometimes a see a occasional reschedulei.e., the 2 processes get
> > scheduled one more time after they are scheduled for the 1st time. I ran
>my
> > code 100 times and observed this behavior 8 out of 100 times. What
>could be
> > the reason?
> > (As I said i want my 2 processes to run together without any reschedule
> > after they are scheduled for the first time).
>
> The only way a real time priority process of SCHED_FIFO gets
>rescheduled, is if the process voluntarily calls schedule (you call a
>system call that calls schedule), or a higher priority process gets
>scheduled. I don't know what your program is doing, or what priorities
>that they are running with to know if something like this has occurred.
>
>Also, if the programs you are running haven't been locked into memory
>(they exist partially on the hard drive still), then it will take time
>to map the code into memory when that code is called, and a schedule
>will occur then as well.
>
>-- Steve
>
>
_________________________________________________________________
Thinking of Marriage.
http://www.bharatmatrimony.com/cgi-bin/bmclicks1.cgi?74 Think
BharatMatrimony.com
next prev parent reply other threads:[~2005-05-02 5:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-07 1:41 scheduler/SCHED_FIFO behaviour Arun Srinivas
2005-04-07 2:27 ` Steven Rostedt
2005-05-01 2:06 ` Arun Srinivas
2005-05-01 15:51 ` Steven Rostedt
2005-05-02 5:27 ` Arun Srinivas [this message]
2005-05-02 10:37 ` Florian Schmidt
2005-05-02 16:33 ` Steven Rostedt
-- strict thread matches above, loose matches on Subject: below --
2005-04-03 23:08 sched /HT processor Steven Rostedt
2005-04-04 23:06 ` scheduler/SCHED_FIFO behaviour Arun Srinivas
2005-04-04 23:17 ` Steven Rostedt
2005-04-05 2:16 ` Arun Srinivas
2005-04-05 3:33 ` Steven Rostedt
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=BAY10-F2709F2A16EEE74732F797FD9270@phx.gbl \
--to=getarunsri@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
/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