From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-arch@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Russell King <rmk@arm.linux.org.uk>
Subject: Re: [patch] sched: remove scheduler locking from arch code
Date: Sun, 27 Mar 2005 13:03:17 +1000 [thread overview]
Message-ID: <42462275.1000101@yahoo.com.au> (raw)
In-Reply-To: <4245631A.1070806@yahoo.com.au>
Nick Piggin wrote:
> Index: linux-2.6/include/linux/init_task.h
> ===================================================================
> --- linux-2.6.orig/include/linux/init_task.h 2005-03-26 19:24:10.000000000 +1100
> +++ linux-2.6/include/linux/init_task.h 2005-03-26 23:55:46.000000000 +1100
> @@ -74,14 +74,13 @@ extern struct group_info init_groups;
> .usage = ATOMIC_INIT(2), \
> .flags = 0, \
> .lock_depth = -1, \
> - .prio = MAX_PRIO-20, \
> - .static_prio = MAX_PRIO-20, \
> + .prio = MAX_PRIO-29, \
> + .static_prio = MAX_PRIO-29, \
> .policy = SCHED_NORMAL, \
> .cpus_allowed = CPU_MASK_ALL, \
> .mm = NULL, \
> .active_mm = &init_mm, \
> .run_list = LIST_HEAD_INIT(tsk.run_list), \
> - .time_slice = HZ, \
> .tasks = LIST_HEAD_INIT(tsk.tasks), \
> .ptrace_children= LIST_HEAD_INIT(tsk.ptrace_children), \
> .ptrace_list = LIST_HEAD_INIT(tsk.ptrace_list), \
This hunk crept in from another patch. I'll fix that up.
prev parent reply other threads:[~2005-03-27 3:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-26 13:26 [patch] sched: remove scheduler locking from arch code Nick Piggin
2005-03-26 13:34 ` [patch][RFC] sched: optimise/cleanup resched_task, idle routines Nick Piggin
2005-03-26 13:34 ` Nick Piggin
2005-03-26 21:36 ` [patch] sched: remove scheduler locking from arch code David S. Miller
2005-03-27 3:03 ` Nick Piggin [this message]
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=42462275.1000101@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=davem@davemloft.net \
--cc=linux-arch@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rmk@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.