public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Clark Williams <williams@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] scheduler include file reorganization
Date: Mon, 11 Feb 2013 10:54:58 +0100	[thread overview]
Message-ID: <20130211095457.GF23932@gmail.com> (raw)
In-Reply-To: <20130208085828.02e61518@riff.lan>


* Clark Williams <williams@redhat.com> wrote:

> I figured that was coming. :)

;-)

> I'll look at it again and see about pulling the 
> autogroup/cgroup stuff into it's own header. After that it's 
> probably going to require some serious changes.
> 
> Any suggestions?

I'd suggest doing it as finegrained as possible - potentially 
one concept at a time. I wouldn't mind a dozen small files in 
include/linux/sched/ - possibly more.

In the end sched.h would include core wakeup/sleep methods that 
tons of drivers rely on, and it would include the 'struct 
task_struct' data type definition (and all its prereqs), which 
we rely on in tons of drivers as well.

Not much else should remain in sched.h - in theory :-)

In terms of build coverage: just build an x86 defconfig with 
perhaps the specific sub-feature (such as autogroups/cgroups) 
turned off/on - I'd suggest for you to not even do allmodconfig 
testing (which is really slow unless you have a cluster of build 
machines), I can test all that and more and fix the fallout 
before applying it.

Thanks,

	Ingo

  reply	other threads:[~2013-02-11  9:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-07 15:46 [PATCH 0/3] scheduler include file reorganization Clark Williams
2013-02-07 18:56 ` Ingo Molnar
2013-02-07 19:13   ` Ingo Molnar
2013-02-07 19:52     ` Ingo Molnar
2013-02-07 21:08       ` Clark Williams
2013-02-08 14:18         ` Ingo Molnar
2013-02-08 14:58           ` Clark Williams
2013-02-11  9:54             ` Ingo Molnar [this message]
2013-02-13  1:29               ` Namhyung Kim
2013-02-13  9:15                 ` Ingo Molnar
2013-02-13 15:19                   ` Clark Williams
2013-02-14  7:59                     ` Namhyung Kim
2013-02-16  3:40                   ` Li Zefan

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=20130211095457.GF23932@gmail.com \
    --to=mingo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=williams@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox