From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Adrian Bunk <bunk@kernel.org>
Cc: Mike Galbraith <efault@gmx.de>, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Dhaval Giani <dhaval@linux.vnet.ibm.com>,
vatsa <vatsa@in.ibm.com>
Subject: Re: [RFC: 2.6 patch] let GROUP_SCHED depend on BROKEN
Date: Tue, 27 May 2008 13:47:29 +0200 [thread overview]
Message-ID: <1211888849.12349.28.camel@twins> (raw)
In-Reply-To: <20080527085830.GA20938@cs181133002.pp.htv.fi>
On Tue, 2008-05-27 at 11:58 +0300, Adrian Bunk wrote:
> I therefore suggest this patch to let GROUP_SCHED depend on BROKEN.
NAK - Most if not all issues have fixes or specific reverts already.
Your suggestion is really quite ridiculous and offensive to me. BROKEN
is for stuff that crashes kernels or corrupts user data. Group
scheduling does neither.
As I've said - and which you so 'tactfully' quoted - group scheduling is
a mathmatically complex topic that we are improving actively. The
feature is not enabled by default and it depends on EXPERIMENTAL.
Adrian - if you care about the subject so much - dive into the code and
help us, instead of becoming an obstacle. These past years you've shown
you're capable of understanding trivial C snippets, here is an
opportunity to show you can do real stuff too.
FYI your attitude in the past few weeks is getting on my nerves - you
act all self important but have not made a single contribution to the
kernel above the level of a janitor-newbie.
next prev parent reply other threads:[~2008-05-27 11:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-27 8:58 [RFC: 2.6 patch] let GROUP_SCHED depend on BROKEN Adrian Bunk
2008-05-27 9:47 ` Mike Galbraith
2008-05-27 10:04 ` Mike Galbraith
2008-05-27 10:26 ` Adrian Bunk
2008-05-27 10:28 ` Alan Cox
2008-05-27 11:27 ` Mike Galbraith
2008-05-27 11:47 ` Peter Zijlstra [this message]
2008-05-27 13:08 ` Adrian Bunk
2008-05-27 14:17 ` Peter Zijlstra
2008-05-27 17:30 ` Thomas Gleixner
2008-05-27 19:18 ` Adrian Bunk
2008-05-27 14:22 ` Ingo Molnar
2008-05-27 17:53 ` Adrian Bunk
2008-05-27 18:17 ` Mike Galbraith
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=1211888849.12349.28.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=dhaval@linux.vnet.ibm.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.org \
--cc=vatsa@in.ibm.com \
/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.