Am Sonntag 29 April 2007 schrieb Prakash Punnoor:
> Am Samstag 28 April 2007 schrieb Ingo Molnar:
> > i'm pleased to announce release -v7 of the CFS scheduler patchset. (The
> > main goal of CFS is to implement "desktop scheduling" with as high
> > quality as technically possible.)
> >
> > The CFS
Am Sonntag 29 April 2007 schrieb Prakash Punnoor:
Am Samstag 28 April 2007 schrieb Ingo Molnar:
i'm pleased to announce release -v7 of the CFS scheduler patchset. (The
main goal of CFS is to implement desktop scheduling with as high
quality as technically possible.)
The CFS patch
* Ting Yang <[EMAIL PROTECTED]> wrote:
>> then how much time is needed for "curr" to build a 2 * 32 difference
>> on fair_key, with every 1 ms it updates fair_key by 1/32 ? 2 * 32 *
>> 32 !
On Thu, May 03, 2007 at 09:48:27PM +0200, Ingo Molnar wrote:
> yes - but the "*32" impacts the
* Ting Yang <[EMAIL PROTECTED]> wrote:
> then how much time is needed for "curr" to build a 2 * 32 difference
> on fair_key, with every 1 ms it updates fair_key by 1/32 ? 2 * 32 *
> 32 !
yes - but the "*32" impacts the rescheduling granularity, the "/32"
impacts the speed of how the key
Hi, Ingo
This is the test case that I think worth discuss and it leads me to
find 2 things.
[...] but there are still some nice issues.
Try running 3 chew.c's, then renicing one to -10, starves others for
some seconds while switching prio-level. Now renice it back to 10, it
starves for
Hi, Ingo
I wrote that email in a hurry, therefore might not explain the
problem clearly. However I do think there is a problem for this part,
after I carefully read the code again. Now I want to try again :-)
Hopefully, this time I will do a right job.
Starting from the following code:
* Ting Yang <[EMAIL PROTECTED]> wrote:
> +s64 __delta = curr->fair_key - p->fair_key;
> +
> +/*
> + * Take scheduling granularity into account - do not
> + * preempt the current task unless the best task has
> + * a larger than sched_granularity fairness advantage:
> + */
Hi, Ingo
This is the test case that I think worth discuss and it leads me to
find 2 things.
[...] but there are still some nice issues.
Try running 3 chew.c's, then renicing one to -10, starves others for
some seconds while switching prio-level. Now renice it back to 10, it
starves
Ingo Molnar wrote:
> * Al Boldi <[EMAIL PROTECTED]> wrote:
> > [...] But I can still see these awful latency blips in the presence of
> > negatively niced chew.c at -10 and two chew.c's at nice 0. [...]
>
> of course: you asked for the two chew's to be treated like that and CFS
> delivered it! :-)
* Al Boldi <[EMAIL PROTECTED]> wrote:
> [...] But I can still see these awful latency blips in the presence of
> negatively niced chew.c at -10 and two chew.c's at nice 0. [...]
of course: you asked for the two chew's to be treated like that and CFS
delivered it! :-)
nice -10 means the two
Ingo Molnar wrote:
> * Ingo Molnar <[EMAIL PROTECTED]> wrote:
> > > [...] but there are still some nice issues.
> > >
> > > Try running 3 chew.c's, then renicing one to -10, starves others for
> > > some seconds while switching prio-level. Now renice it back to 10,
> > > it starves for up to
Ingo Molnar wrote:
> * Al Boldi <[EMAIL PROTECTED]> wrote:
> > > i'm pleased to announce release -v7 of the CFS scheduler patchset.
> > > (The main goal of CFS is to implement "desktop scheduling" with as
> > > high quality as technically possible.)
> > >
> > >
> > > As usual, any sort of
* Ingo Molnar <[EMAIL PROTECTED]> wrote:
> > [...] but there are still some nice issues.
> >
> > Try running 3 chew.c's, then renicing one to -10, starves others for
> > some seconds while switching prio-level. Now renice it back to 10,
> > it starves for up to 45sec.
>
> ok - to make sure
* Al Boldi <[EMAIL PROTECTED]> wrote:
> > i'm pleased to announce release -v7 of the CFS scheduler patchset.
> > (The main goal of CFS is to implement "desktop scheduling" with as
> > high quality as technically possible.)
> :
> :
> > As usual, any sort of feedback, bugreport, fix and
* Al Boldi [EMAIL PROTECTED] wrote:
i'm pleased to announce release -v7 of the CFS scheduler patchset.
(The main goal of CFS is to implement desktop scheduling with as
high quality as technically possible.)
:
:
As usual, any sort of feedback, bugreport, fix and suggestion is
more
* Ingo Molnar [EMAIL PROTECTED] wrote:
[...] but there are still some nice issues.
Try running 3 chew.c's, then renicing one to -10, starves others for
some seconds while switching prio-level. Now renice it back to 10,
it starves for up to 45sec.
ok - to make sure i understood
Ingo Molnar wrote:
* Al Boldi [EMAIL PROTECTED] wrote:
i'm pleased to announce release -v7 of the CFS scheduler patchset.
(The main goal of CFS is to implement desktop scheduling with as
high quality as technically possible.)
As usual, any sort of feedback, bugreport, fix and
Ingo Molnar wrote:
* Ingo Molnar [EMAIL PROTECTED] wrote:
[...] but there are still some nice issues.
Try running 3 chew.c's, then renicing one to -10, starves others for
some seconds while switching prio-level. Now renice it back to 10,
it starves for up to 45sec.
ok - to
* Al Boldi [EMAIL PROTECTED] wrote:
[...] But I can still see these awful latency blips in the presence of
negatively niced chew.c at -10 and two chew.c's at nice 0. [...]
of course: you asked for the two chew's to be treated like that and CFS
delivered it! :-)
nice -10 means the two
Ingo Molnar wrote:
* Al Boldi [EMAIL PROTECTED] wrote:
[...] But I can still see these awful latency blips in the presence of
negatively niced chew.c at -10 and two chew.c's at nice 0. [...]
of course: you asked for the two chew's to be treated like that and CFS
delivered it! :-)
nice
Hi, Ingo
This is the test case that I think worth discuss and it leads me to
find 2 things.
[...] but there are still some nice issues.
Try running 3 chew.c's, then renicing one to -10, starves others for
some seconds while switching prio-level. Now renice it back to 10, it
starves
* Ting Yang [EMAIL PROTECTED] wrote:
+s64 __delta = curr-fair_key - p-fair_key;
+
+/*
+ * Take scheduling granularity into account - do not
+ * preempt the current task unless the best task has
+ * a larger than sched_granularity fairness advantage:
+ */
+if
Hi, Ingo
I wrote that email in a hurry, therefore might not explain the
problem clearly. However I do think there is a problem for this part,
after I carefully read the code again. Now I want to try again :-)
Hopefully, this time I will do a right job.
Starting from the following code:
Hi, Ingo
This is the test case that I think worth discuss and it leads me to
find 2 things.
[...] but there are still some nice issues.
Try running 3 chew.c's, then renicing one to -10, starves others for
some seconds while switching prio-level. Now renice it back to 10, it
starves for
* Ting Yang [EMAIL PROTECTED] wrote:
then how much time is needed for curr to build a 2 * 32 difference
on fair_key, with every 1 ms it updates fair_key by 1/32 ? 2 * 32 *
32 !
yes - but the *32 impacts the rescheduling granularity, the /32
impacts the speed of how the key moves. So the
* Ting Yang [EMAIL PROTECTED] wrote:
then how much time is needed for curr to build a 2 * 32 difference
on fair_key, with every 1 ms it updates fair_key by 1/32 ? 2 * 32 *
32 !
On Thu, May 03, 2007 at 09:48:27PM +0200, Ingo Molnar wrote:
yes - but the *32 impacts the rescheduling
Ingo Molnar wrote:
i'm pleased to announce release -v7 of the CFS scheduler patchset. (The
main goal of CFS is to implement "desktop scheduling" with as high
quality as technically possible.)
The CFS patch against v2.6.21 (or against v2.6.20.8) can be downloaded
from the usual place:
On Sat, Apr 28, 2007 at 05:25:39PM +0200, Ingo Molnar wrote:
> i'm pleased to announce release -v7 of the CFS scheduler patchset. (The
> main goal of CFS is to implement "desktop scheduling" with as high
> quality as technically possible.)
+unsigned int sysctl_sched_granularity __read_mostly =
Hi Ingo;
29 Nis 2007 Paz tarihinde, Ingo Molnar şunları yazmıştı:
> * S.Çağlar Onur <[EMAIL PROTECTED]> wrote:
> > I'll report if i can find any reproducable problem, so far CFSv7 works
> > as expected :)
After complete 2 day usage, i still can't reproduce previous problems. And
even can
Hi Ingo;
29 Nis 2007 Paz tarihinde, Ingo Molnar şunları yazmıştı:
* S.Çağlar Onur [EMAIL PROTECTED] wrote:
I'll report if i can find any reproducable problem, so far CFSv7 works
as expected :)
After complete 2 day usage, i still can't reproduce previous problems. And
even can manage to
On Sat, Apr 28, 2007 at 05:25:39PM +0200, Ingo Molnar wrote:
i'm pleased to announce release -v7 of the CFS scheduler patchset. (The
main goal of CFS is to implement desktop scheduling with as high
quality as technically possible.)
+unsigned int sysctl_sched_granularity __read_mostly =
Ingo Molnar wrote:
i'm pleased to announce release -v7 of the CFS scheduler patchset. (The
main goal of CFS is to implement desktop scheduling with as high
quality as technically possible.)
The CFS patch against v2.6.21 (or against v2.6.20.8) can be downloaded
from the usual place:
Ingo Molnar wrote:
>
> i'm pleased to announce release -v7 of the CFS scheduler patchset. (The
> main goal of CFS is to implement "desktop scheduling" with as high
> quality as technically possible.)
:
:
> As usual, any sort of feedback, bugreport, fix and suggestion is more
> than welcome,
This
On Sunday 29 April 2007, Ingo Molnar wrote:
> * S.Çağlar Onur <[EMAIL PROTECTED]> wrote:
> > I'll report if i can find any reproducable problem, so far CFSv7 works
> > as expected :)
>
> ok :)
>
> Ingo
One small regression: I worked for hours with cfs v7 as scheduler while
listening to
Am Samstag 28 April 2007 schrieb Ingo Molnar:
> i'm pleased to announce release -v7 of the CFS scheduler patchset. (The
> main goal of CFS is to implement "desktop scheduling" with as high
> quality as technically possible.)
>
> The CFS patch against v2.6.21 (or against v2.6.20.8) can be
* S.Çağlar Onur <[EMAIL PROTECTED]> wrote:
> I'll report if i can find any reproducable problem, so far CFSv7 works
> as expected :)
ok :)
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info
29 Nis 2007 Paz tarihinde, Ingo Molnar şunları yazmıştı:
> > [...] and there were no regression instead of my daydreams) or im too
> > tired to understand the differences.
>
> could the CPU have dropped speed for that bootup (some CPUs do that
> automatically upon overheating), or perhaps if you
* S.Çağlar Onur <[EMAIL PROTECTED]> wrote:
> Ingo, please ignore my first report until i found a proper way to
> reproduce the slowness cause currently CFS-v7, CFS-v7 + "renice
> patch", CFS-v7 + renice + your private mail suggestions and CFS-v6 +
> "PI support for futexes patch" seems works
* S.Çağlar Onur [EMAIL PROTECTED] wrote:
Ingo, please ignore my first report until i found a proper way to
reproduce the slowness cause currently CFS-v7, CFS-v7 + renice
patch, CFS-v7 + renice + your private mail suggestions and CFS-v6 +
PI support for futexes patch seems works equally
29 Nis 2007 Paz tarihinde, Ingo Molnar şunları yazmıştı:
[...] and there were no regression instead of my daydreams) or im too
tired to understand the differences.
could the CPU have dropped speed for that bootup (some CPUs do that
automatically upon overheating), or perhaps if you are
* S.Çağlar Onur [EMAIL PROTECTED] wrote:
I'll report if i can find any reproducable problem, so far CFSv7 works
as expected :)
ok :)
Ingo
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Am Samstag 28 April 2007 schrieb Ingo Molnar:
i'm pleased to announce release -v7 of the CFS scheduler patchset. (The
main goal of CFS is to implement desktop scheduling with as high
quality as technically possible.)
The CFS patch against v2.6.21 (or against v2.6.20.8) can be downloaded
from
On Sunday 29 April 2007, Ingo Molnar wrote:
* S.Çağlar Onur [EMAIL PROTECTED] wrote:
I'll report if i can find any reproducable problem, so far CFSv7 works
as expected :)
ok :)
Ingo
One small regression: I worked for hours with cfs v7 as scheduler while
listening to music (with
Ingo Molnar wrote:
i'm pleased to announce release -v7 of the CFS scheduler patchset. (The
main goal of CFS is to implement desktop scheduling with as high
quality as technically possible.)
:
:
As usual, any sort of feedback, bugreport, fix and suggestion is more
than welcome,
This one
28 Nis 2007 Cts tarihinde, Ingo Molnar şunları yazmıştı:
> * S.Çağlar Onur <[EMAIL PROTECTED]> wrote:
> > If you want some more output/info etc. please just say, i have both v6
> > and v7 available.
>
> could you try the auto-renice patch ontop of -v7:
>
>
* S.Çağlar Onur <[EMAIL PROTECTED]> wrote:
> If you want some more output/info etc. please just say, i have both v6
> and v7 available.
could you try the auto-renice patch ontop of -v7:
http://people.redhat.com/mingo/cfs-scheduler/sched-cfs-auto-renice.patch
does this make it behave like
28 Nis 2007 Cts tarihinde, S.Çağlar Onur şunları yazmıştı:
> Also somehow boot takes longer;
>
> v6;
> Apr 28 16:40:41 (up 10.57) /sbin/mudur.py sysinit
> Apr 28 13:40:49 (up 17.75) /sbin/mudur.py boot
> Apr 28 13:41:00 (up 28.61) /sbin/mudur.py default
>
> v7;
> Apr 29 00:35:49 (up 10.61)
28 Nis 2007 Cts tarihinde, Ingo Molnar şunları yazmıştı:
> - feature removal: remove the X auto-renicing feature, CONFIG_BOOST_X.
This the the first time i use CFS with without X auto-renicing and i think its
not smooth as before :(
While compiling something (say alsa-drivers) with just
i'm pleased to announce release -v7 of the CFS scheduler patchset. (The
main goal of CFS is to implement "desktop scheduling" with as high
quality as technically possible.)
The CFS patch against v2.6.21 (or against v2.6.20.8) can be downloaded
from the usual place:
i'm pleased to announce release -v7 of the CFS scheduler patchset. (The
main goal of CFS is to implement desktop scheduling with as high
quality as technically possible.)
The CFS patch against v2.6.21 (or against v2.6.20.8) can be downloaded
from the usual place:
28 Nis 2007 Cts tarihinde, Ingo Molnar şunları yazmıştı:
- feature removal: remove the X auto-renicing feature, CONFIG_BOOST_X.
This the the first time i use CFS with without X auto-renicing and i think its
not smooth as before :(
While compiling something (say alsa-drivers) with just make
* S.Çağlar Onur [EMAIL PROTECTED] wrote:
If you want some more output/info etc. please just say, i have both v6
and v7 available.
could you try the auto-renice patch ontop of -v7:
http://people.redhat.com/mingo/cfs-scheduler/sched-cfs-auto-renice.patch
does this make it behave like -v6?
28 Nis 2007 Cts tarihinde, S.Çağlar Onur şunları yazmıştı:
Also somehow boot takes longer;
v6;
Apr 28 16:40:41 (up 10.57) /sbin/mudur.py sysinit
Apr 28 13:40:49 (up 17.75) /sbin/mudur.py boot
Apr 28 13:41:00 (up 28.61) /sbin/mudur.py default
v7;
Apr 29 00:35:49 (up 10.61) /sbin/mudur.py
28 Nis 2007 Cts tarihinde, Ingo Molnar şunları yazmıştı:
* S.Çağlar Onur [EMAIL PROTECTED] wrote:
If you want some more output/info etc. please just say, i have both v6
and v7 available.
could you try the auto-renice patch ontop of -v7:
54 matches
Mail list logo
