Patch Output

bfs357-penalise_fork_depth_account_threads.patch.out (text/plain), 16.07 KB, created by Dan Reidy on 2011-04-24 23:14:49 UTC

***** bfs357-penalise_fork_depth_account_threads.patch *****

============================================================

PATCH COMMAND:  patch -p0 -g0 -E --no-backup-if-mismatch < '/var/tmp/distfiles/bfs357-penalise_fork_depth_account_threads.patch'

============================================================
can't find file to patch at input line 50
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Make it possible to have interactivity and responsiveness at very high load
|levels by making deadlines offset by the fork depth from init. This has a
|similar effect to 'nice'ing loads that are fork heavy. 'make' is a perfect
|example of this and will, with fork_depth_penalty enabled, be felt as much
|at 'make -j24' as it normally would be with just 'make'.
|
|Note that this drastically affects CPU distribution, and also has the
|indirect side effect of partitioning CPU entitlement to different users as
|well. No assumption as to CPU distribution should be made based on past
|behaviour.
|
|This is achieved by separating out forks to new processes vs new threads.
|When a new process is detected, its fork depth is inherited from its parent
|across fork() and then is incremented by one. That fork_depth is then used
|to cause a relative offset of its deadline.
|
|This feature is enabled in this patch by default and can be optionally
|disabled.
|
|Threads are kept at the same fork_depth as their parent process, and can
|optionally have their CPU entitlement all managed as one process together
|by enabling the group_thread_accounting feature. This feature is disabled
|by default in this patch, as many desktop applications such as firefox,
|amarok, etc are multithreaded. By disabling this feature and enabling the
|fork_depth_penalty feature (default) it favours CPU towards desktop
|applications.
|
|Extensive testing is required to ensure this does not cause regressions in
|common workloads.
|
|There are two sysctls to enable/disable these features.
|
|They are in /proc/sys/kernel/
|
|group_thread_accounting - groups CPU accounting by threads
|fork_depth_penalty - penalises according to depth of forking from init
|
|-ck
|
|---
| include/linux/sched.h |    7 +++
| kernel/sched_bfs.c    |   88 ++++++++++++++++++++++++++++++++++++++++++++++----
| kernel/sysctl.c       |   20 +++++++++++
| 3 files changed, 108 insertions(+), 7 deletions(-)
|
|Index: linux-2.6.36-rc7-ck1/include/linux/sched.h
|===================================================================
|--- linux-2.6.36-rc7-ck1.orig/include/linux/sched.h	2010-10-08 09:39:38.016240768 +1100
|+++ linux-2.6.36-rc7-ck1/include/linux/sched.h	2010-10-08 09:39:53.575007838 +1100
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 71
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: linux-2.6.36-rc7-ck1/kernel/sched_bfs.c
|===================================================================
|--- linux-2.6.36-rc7-ck1.orig/kernel/sched_bfs.c	2010-10-08 09:39:37.918242270 +1100
|+++ linux-2.6.36-rc7-ck1/kernel/sched_bfs.c	2010-10-08 11:16:01.382198622 +1100
--------------------------
No file to patch.  Skipping patch.
10 out of 10 hunks ignored
can't find file to patch at input line 249
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: linux-2.6.36-rc7-ck1/kernel/sysctl.c
|===================================================================
|--- linux-2.6.36-rc7-ck1.orig/kernel/sysctl.c	2010-10-08 09:39:11.603648964 +1100
|+++ linux-2.6.36-rc7-ck1/kernel/sysctl.c	2010-10-08 09:39:53.579007778 +1100
--------------------------
No file to patch.  Skipping patch.
2 out of 2 hunks ignored
============================================================

PATCH COMMAND:  patch -p1 -g0 -E --no-backup-if-mismatch < '/var/tmp/distfiles/bfs357-penalise_fork_depth_account_threads.patch'

============================================================
patching file include/linux/sched.h
Hunk #1 FAILED at 1187.
1 out of 1 hunk FAILED -- saving rejects to file include/linux/sched.h.rej
patching file kernel/sched_bfs.c
Hunk #1 succeeded at 141 (offset 2 lines).
Hunk #2 succeeded at 683 (offset 13 lines).
Hunk #3 succeeded at 993 (offset -1 lines).
Hunk #4 succeeded at 1016 (offset -1 lines).
Hunk #5 succeeded at 1035 (offset -1 lines).
Hunk #6 succeeded at 1756 (offset 78 lines).
Hunk #7 succeeded at 2798 (offset 227 lines).
Hunk #8 succeeded at 2833 (offset 232 lines).
Hunk #9 succeeded at 3837 (offset 252 lines).
Hunk #10 succeeded at 3849 (offset 252 lines).
patching file kernel/sysctl.c
Hunk #1 succeeded at 122 (offset 1 line).
Hunk #2 succeeded at 854 (offset 18 lines).
============================================================

PATCH COMMAND:  patch -p2 -g0 -E --no-backup-if-mismatch < '/var/tmp/distfiles/bfs357-penalise_fork_depth_account_threads.patch'

============================================================
can't find file to patch at input line 50
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Make it possible to have interactivity and responsiveness at very high load
|levels by making deadlines offset by the fork depth from init. This has a
|similar effect to 'nice'ing loads that are fork heavy. 'make' is a perfect
|example of this and will, with fork_depth_penalty enabled, be felt as much
|at 'make -j24' as it normally would be with just 'make'.
|
|Note that this drastically affects CPU distribution, and also has the
|indirect side effect of partitioning CPU entitlement to different users as
|well. No assumption as to CPU distribution should be made based on past
|behaviour.
|
|This is achieved by separating out forks to new processes vs new threads.
|When a new process is detected, its fork depth is inherited from its parent
|across fork() and then is incremented by one. That fork_depth is then used
|to cause a relative offset of its deadline.
|
|This feature is enabled in this patch by default and can be optionally
|disabled.
|
|Threads are kept at the same fork_depth as their parent process, and can
|optionally have their CPU entitlement all managed as one process together
|by enabling the group_thread_accounting feature. This feature is disabled
|by default in this patch, as many desktop applications such as firefox,
|amarok, etc are multithreaded. By disabling this feature and enabling the
|fork_depth_penalty feature (default) it favours CPU towards desktop
|applications.
|
|Extensive testing is required to ensure this does not cause regressions in
|common workloads.
|
|There are two sysctls to enable/disable these features.
|
|They are in /proc/sys/kernel/
|
|group_thread_accounting - groups CPU accounting by threads
|fork_depth_penalty - penalises according to depth of forking from init
|
|-ck
|
|---
| include/linux/sched.h |    7 +++
| kernel/sched_bfs.c    |   88 ++++++++++++++++++++++++++++++++++++++++++++++----
| kernel/sysctl.c       |   20 +++++++++++
| 3 files changed, 108 insertions(+), 7 deletions(-)
|
|Index: linux-2.6.36-rc7-ck1/include/linux/sched.h
|===================================================================
|--- linux-2.6.36-rc7-ck1.orig/include/linux/sched.h	2010-10-08 09:39:38.016240768 +1100
|+++ linux-2.6.36-rc7-ck1/include/linux/sched.h	2010-10-08 09:39:53.575007838 +1100
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 71
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: linux-2.6.36-rc7-ck1/kernel/sched_bfs.c
|===================================================================
|--- linux-2.6.36-rc7-ck1.orig/kernel/sched_bfs.c	2010-10-08 09:39:37.918242270 +1100
|+++ linux-2.6.36-rc7-ck1/kernel/sched_bfs.c	2010-10-08 11:16:01.382198622 +1100
--------------------------
No file to patch.  Skipping patch.
10 out of 10 hunks ignored
can't find file to patch at input line 249
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: linux-2.6.36-rc7-ck1/kernel/sysctl.c
|===================================================================
|--- linux-2.6.36-rc7-ck1.orig/kernel/sysctl.c	2010-10-08 09:39:11.603648964 +1100
|+++ linux-2.6.36-rc7-ck1/kernel/sysctl.c	2010-10-08 09:39:53.579007778 +1100
--------------------------
No file to patch.  Skipping patch.
2 out of 2 hunks ignored
============================================================

PATCH COMMAND:  patch -p3 -g0 -E --no-backup-if-mismatch < '/var/tmp/distfiles/bfs357-penalise_fork_depth_account_threads.patch'

============================================================
can't find file to patch at input line 50
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Make it possible to have interactivity and responsiveness at very high load
|levels by making deadlines offset by the fork depth from init. This has a
|similar effect to 'nice'ing loads that are fork heavy. 'make' is a perfect
|example of this and will, with fork_depth_penalty enabled, be felt as much
|at 'make -j24' as it normally would be with just 'make'.
|
|Note that this drastically affects CPU distribution, and also has the
|indirect side effect of partitioning CPU entitlement to different users as
|well. No assumption as to CPU distribution should be made based on past
|behaviour.
|
|This is achieved by separating out forks to new processes vs new threads.
|When a new process is detected, its fork depth is inherited from its parent
|across fork() and then is incremented by one. That fork_depth is then used
|to cause a relative offset of its deadline.
|
|This feature is enabled in this patch by default and can be optionally
|disabled.
|
|Threads are kept at the same fork_depth as their parent process, and can
|optionally have their CPU entitlement all managed as one process together
|by enabling the group_thread_accounting feature. This feature is disabled
|by default in this patch, as many desktop applications such as firefox,
|amarok, etc are multithreaded. By disabling this feature and enabling the
|fork_depth_penalty feature (default) it favours CPU towards desktop
|applications.
|
|Extensive testing is required to ensure this does not cause regressions in
|common workloads.
|
|There are two sysctls to enable/disable these features.
|
|They are in /proc/sys/kernel/
|
|group_thread_accounting - groups CPU accounting by threads
|fork_depth_penalty - penalises according to depth of forking from init
|
|-ck
|
|---
| include/linux/sched.h |    7 +++
| kernel/sched_bfs.c    |   88 ++++++++++++++++++++++++++++++++++++++++++++++----
| kernel/sysctl.c       |   20 +++++++++++
| 3 files changed, 108 insertions(+), 7 deletions(-)
|
|Index: linux-2.6.36-rc7-ck1/include/linux/sched.h
|===================================================================
|--- linux-2.6.36-rc7-ck1.orig/include/linux/sched.h	2010-10-08 09:39:38.016240768 +1100
|+++ linux-2.6.36-rc7-ck1/include/linux/sched.h	2010-10-08 09:39:53.575007838 +1100
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
missing header for unified diff at line 71 of patch
can't find file to patch at input line 71
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: linux-2.6.36-rc7-ck1/kernel/sched_bfs.c
|===================================================================
|--- linux-2.6.36-rc7-ck1.orig/kernel/sched_bfs.c	2010-10-08 09:39:37.918242270 +1100
|+++ linux-2.6.36-rc7-ck1/kernel/sched_bfs.c	2010-10-08 11:16:01.382198622 +1100
--------------------------
No file to patch.  Skipping patch.
10 out of 10 hunks ignored
missing header for unified diff at line 249 of patch
can't find file to patch at input line 249
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: linux-2.6.36-rc7-ck1/kernel/sysctl.c
|===================================================================
|--- linux-2.6.36-rc7-ck1.orig/kernel/sysctl.c	2010-10-08 09:39:11.603648964 +1100
|+++ linux-2.6.36-rc7-ck1/kernel/sysctl.c	2010-10-08 09:39:53.579007778 +1100
--------------------------
No file to patch.  Skipping patch.
2 out of 2 hunks ignored
============================================================

PATCH COMMAND:  patch -p4 -g0 -E --no-backup-if-mismatch < '/var/tmp/distfiles/bfs357-penalise_fork_depth_account_threads.patch'

============================================================
missing header for unified diff at line 50 of patch
can't find file to patch at input line 50
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Make it possible to have interactivity and responsiveness at very high load
|levels by making deadlines offset by the fork depth from init. This has a
|similar effect to 'nice'ing loads that are fork heavy. 'make' is a perfect
|example of this and will, with fork_depth_penalty enabled, be felt as much
|at 'make -j24' as it normally would be with just 'make'.
|
|Note that this drastically affects CPU distribution, and also has the
|indirect side effect of partitioning CPU entitlement to different users as
|well. No assumption as to CPU distribution should be made based on past
|behaviour.
|
|This is achieved by separating out forks to new processes vs new threads.
|When a new process is detected, its fork depth is inherited from its parent
|across fork() and then is incremented by one. That fork_depth is then used
|to cause a relative offset of its deadline.
|
|This feature is enabled in this patch by default and can be optionally
|disabled.
|
|Threads are kept at the same fork_depth as their parent process, and can
|optionally have their CPU entitlement all managed as one process together
|by enabling the group_thread_accounting feature. This feature is disabled
|by default in this patch, as many desktop applications such as firefox,
|amarok, etc are multithreaded. By disabling this feature and enabling the
|fork_depth_penalty feature (default) it favours CPU towards desktop
|applications.
|
|Extensive testing is required to ensure this does not cause regressions in
|common workloads.
|
|There are two sysctls to enable/disable these features.
|
|They are in /proc/sys/kernel/
|
|group_thread_accounting - groups CPU accounting by threads
|fork_depth_penalty - penalises according to depth of forking from init
|
|-ck
|
|---
| include/linux/sched.h |    7 +++
| kernel/sched_bfs.c    |   88 ++++++++++++++++++++++++++++++++++++++++++++++----
| kernel/sysctl.c       |   20 +++++++++++
| 3 files changed, 108 insertions(+), 7 deletions(-)
|
|Index: linux-2.6.36-rc7-ck1/include/linux/sched.h
|===================================================================
|--- linux-2.6.36-rc7-ck1.orig/include/linux/sched.h	2010-10-08 09:39:38.016240768 +1100
|+++ linux-2.6.36-rc7-ck1/include/linux/sched.h	2010-10-08 09:39:53.575007838 +1100
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
missing header for unified diff at line 71 of patch
can't find file to patch at input line 71
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: linux-2.6.36-rc7-ck1/kernel/sched_bfs.c
|===================================================================
|--- linux-2.6.36-rc7-ck1.orig/kernel/sched_bfs.c	2010-10-08 09:39:37.918242270 +1100
|+++ linux-2.6.36-rc7-ck1/kernel/sched_bfs.c	2010-10-08 11:16:01.382198622 +1100
--------------------------
No file to patch.  Skipping patch.
10 out of 10 hunks ignored
missing header for unified diff at line 249 of patch
can't find file to patch at input line 249
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: linux-2.6.36-rc7-ck1/kernel/sysctl.c
|===================================================================
|--- linux-2.6.36-rc7-ck1.orig/kernel/sysctl.c	2010-10-08 09:39:11.603648964 +1100
|+++ linux-2.6.36-rc7-ck1/kernel/sysctl.c	2010-10-08 09:39:53.579007778 +1100
--------------------------
No file to patch.  Skipping patch.
2 out of 2 hunks ignored