From: Paul Jackson <pj@sgi.com>
To: akpm@linux-foundation.org
Cc: menage@google.com, seto.hidetoshi@jp.fujitsu.com, mingo@elte.hu,
linux-kernel@vger.kernel.org,
Max Krasnyanskiy <maxk@qualcomm.com>, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>,
Oleg Nesterov <oleg@tv-sign.ru>,
Steven Rostedt <rostedt@goodmis.org>,
David Rientjes <rientjes@google.com>
Subject: Reverting per-cpuset "system" (IRQ affinity) patch (was: Fix cpuset sched_relax_domain_level control file)
Date: Tue, 6 May 2008 22:38:59 -0500 [thread overview]
Message-ID: <20080506223859.0b4fa876.pj@sgi.com> (raw)
In-Reply-To: <20080506204054.564fff32.pj@sgi.com>
pj wrote:
> What's the easiest way to get from where we are now, to a world
> without that patch?
Would it help, Andrew, if I proposed a patch that went into your latest
mmtom stack, right after the three patches:
origin.patch
linux-next.patch
Paul Menage's latest "Fix cpuset sched_relax_domain_level control file"
that reverted the cpuset "system" patch (this being a patch that added
a per-cpuset file called "system", which could be used to do things
such as help manage the assignment of IRQs to CPUs.)
I suspect that some of Ingo, Max Krasnyanskiy, or Peter Zijlstra will
not be happy with my doing this, but I'm pretty sure that the "system"
patch needs more work before we have agreement on the API. I really
don't want to add the API of that current patch "as is" to the kernel.
I've added several of the people who were part of the preceding threads
on this discussion to the CC list.
I'm cooking up such a patch now -- I've gotten to the point that it
applies and builds; now I am about to see how badly it breaks the
remaining 426 patches in the mmtom stack.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.940.382.4214
next prev parent reply other threads:[~2008-05-07 3:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 1:08 [PATCH] Fix cpuset sched_relax_domain_level control file Paul Menage
2008-05-07 1:21 ` Li Zefan
2008-05-07 1:31 ` Andrew Morton
2008-05-07 1:40 ` Paul Jackson
2008-05-07 3:38 ` Paul Jackson [this message]
2008-05-07 3:44 ` Reverting per-cpuset "system" (IRQ affinity) patch (was: Fix cpuset sched_relax_domain_level control file) Andrew Morton
2008-05-07 3:52 ` Paul Jackson
2008-05-07 6:44 ` Peter Zijlstra
2008-05-08 17:56 ` Reverting per-cpuset "system" (IRQ affinity) patch Max Krasnyansky
2008-05-09 10:22 ` Ingo Molnar
2008-05-09 11:26 ` Paul Jackson
2008-05-21 0:46 ` Max Krasnyanskiy
2008-05-07 1:38 ` [PATCH] Fix cpuset sched_relax_domain_level control file Andrew Morton
2008-05-07 1:41 ` Paul Menage
2008-05-07 9:48 ` Adrian Bunk
2008-05-07 15:08 ` Andrew Morton
2008-05-07 1:46 ` Li Zefan
2008-05-07 1:49 ` Paul Jackson
2008-05-07 1:51 ` Paul Menage
2008-05-07 1:58 ` Paul Jackson
2008-05-07 2:08 ` Andrew Morton
2008-05-07 2:11 ` Paul Jackson
2008-05-07 2:15 ` Paul Menage
2008-05-07 2:28 ` Andrew Morton
2008-05-07 2:32 ` Paul Jackson
2008-05-07 2:12 ` Li Zefan
2008-05-07 2:17 ` Paul Jackson
2008-05-07 2:27 ` Hidetoshi Seto
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=20080506223859.0b4fa876.pj@sgi.com \
--to=pj@sgi.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.com \
--cc=menage@google.com \
--cc=mingo@elte.hu \
--cc=oleg@tv-sign.ru \
--cc=rientjes@google.com \
--cc=rostedt@goodmis.org \
--cc=seto.hidetoshi@jp.fujitsu.com \
--cc=tglx@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox