On Monday 09 April 2007 16:09, Andrew Morton wrote:
> On Sat, 07 Apr 2007 16:31:39 +0900 Satoru Takeuchi
<[EMAIL PROTECTED]> wrote:
> > When I was examining the following program ...
> >
> > 1. There are a large amount of small jobs takes several msecs,
> > and the number of job increases
On Monday 09 April 2007 16:09, Andrew Morton wrote:
On Sat, 07 Apr 2007 16:31:39 +0900 Satoru Takeuchi
[EMAIL PROTECTED] wrote:
When I was examining the following program ...
1. There are a large amount of small jobs takes several msecs,
and the number of job increases constantly.
> > This comes at an awkward time, because we might well merge the
> > staircase/deadline work into 2.6.22, and I think it rewrites the part of
> > the scheduler which is causing the problems you're observing.
> >
> > Has anyone verified that SD fixes this problem and the one at
> >
This comes at an awkward time, because we might well merge the
staircase/deadline work into 2.6.22, and I think it rewrites the part of
the scheduler which is causing the problems you're observing.
Has anyone verified that SD fixes this problem and the one at
> > b) Doesn't add extra field and have thread's parent the creater, which is
> > same as process creation. However it has many side effects, for example,
> > we also need to change sys_getppid() implementation.
>
> can't understand this, sorry.
Sorry for my obscure English, perhaps I
On 04/09, Oleg Nesterov wrote:
>
> Satoru Takeuchi wrote:
> >
> > a) On sched_fork, the creator share its timeslice with new process.
> > b) On sched_exit, if the exiting process didn't exhaust its first
> > timeslice yet, it gives its timeslice to the parent.
> >
> > It has no problem on
Satoru Takeuchi wrote:
>
> a) On sched_fork, the creator share its timeslice with new process.
> b) On sched_exit, if the exiting process didn't exhaust its first
> timeslice yet, it gives its timeslice to the parent.
>
> It has no problem on the process model since the creator is the
On Sun, 2007-04-08 at 23:09 -0700, Andrew Morton wrote:
> On Sat, 07 Apr 2007 16:31:39 +0900 Satoru Takeuchi <[EMAIL PROTECTED]> wrote:
>
> > When I was examining the following program ...
> >
> > 1. There are a large amount of small jobs takes several msecs,
> > and the number of job
On Sat, 07 Apr 2007 16:31:39 +0900 Satoru Takeuchi <[EMAIL PROTECTED]> wrote:
> When I was examining the following program ...
>
> 1. There are a large amount of small jobs takes several msecs,
> and the number of job increases constantly.
> 2. The process creates a thread or a process
On Sat, 07 Apr 2007 16:31:39 +0900 Satoru Takeuchi [EMAIL PROTECTED] wrote:
When I was examining the following program ...
1. There are a large amount of small jobs takes several msecs,
and the number of job increases constantly.
2. The process creates a thread or a process per job
On Sun, 2007-04-08 at 23:09 -0700, Andrew Morton wrote:
On Sat, 07 Apr 2007 16:31:39 +0900 Satoru Takeuchi [EMAIL PROTECTED] wrote:
When I was examining the following program ...
1. There are a large amount of small jobs takes several msecs,
and the number of job increases
Satoru Takeuchi wrote:
a) On sched_fork, the creator share its timeslice with new process.
b) On sched_exit, if the exiting process didn't exhaust its first
timeslice yet, it gives its timeslice to the parent.
It has no problem on the process model since the creator is the parent.
On 04/09, Oleg Nesterov wrote:
Satoru Takeuchi wrote:
a) On sched_fork, the creator share its timeslice with new process.
b) On sched_exit, if the exiting process didn't exhaust its first
timeslice yet, it gives its timeslice to the parent.
It has no problem on the process
b) Doesn't add extra field and have thread's parent the creater, which is
same as process creation. However it has many side effects, for example,
we also need to change sys_getppid() implementation.
can't understand this, sorry.
Sorry for my obscure English, perhaps I need more
At Sat, 07 Apr 2007 16:31:39 +0900,
Satoru Takeuchi wrote:
> Test programs(attached in the mail):
>
> - satprocess.c: Process model. It creates a child process and wait for it
>several times. Each child process exits immediately.
> - satthread.c: Thread model. It
Hi Ingo and all,
When I was examining the following program ...
1. There are a large amount of small jobs takes several msecs,
and the number of job increases constantly.
2. The process creates a thread or a process per job (I examined both
the thread model and the process model).
Hi Ingo and all,
When I was examining the following program ...
1. There are a large amount of small jobs takes several msecs,
and the number of job increases constantly.
2. The process creates a thread or a process per job (I examined both
the thread model and the process model).
At Sat, 07 Apr 2007 16:31:39 +0900,
Satoru Takeuchi wrote:
Test programs(attached in the mail):
- satprocess.c: Process model. It creates a child process and wait for it
several times. Each child process exits immediately.
- satthread.c: Thread model. It creates a
18 matches
Mail list logo
