* Clark Williams <willi...@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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
