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>, Ingo Molnar <mingo@elte.hu>,
	Steven Rostedt <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHv2 2/2] sched/rt:  add a tuning knob to allow changing SCHED_RR timeslice
Date: Mon, 4 Feb 2013 12:01:01 +0100	[thread overview]
Message-ID: <20130204110101.GC24173@gmail.com> (raw)
In-Reply-To: <20130203200316.63c15a79@riff.lan>


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

> On Sun, 3 Feb 2013 19:57:09 +0100
> Ingo Molnar <mingo@kernel.org> wrote:
> 
> > 
> > * Ingo Molnar <mingo@kernel.org> wrote:
> > 
> > > The first patch looks good, I've applied it.
> > 
> > I've skipped this one after all, as it sometimes generates:
> > 
> > include/linux/sched/sysctl.h:108:41: warning: ???struct signal_struct??? declared inside parameter list [enabled by default]
> > 
> > Sometimes doesn't built kernel/sched/auto_group.c. So those bits 
> > probably want to move into a separate sched/auto_group.h header 
> > or so.
> > 
> > But, more fundamentally, I think sched.h should not include the 
> > new sched/sysctl.h file. The whole point is to move out bits 
> > from sched.h and decouple them from sched.h - to shrink sched.h 
> > in the long run.
> > 
> > Thanks,
> > 
> > 	Ingo
> 
> Ahh, you wanted to not only reduce the size of sched.h you 
> want to reduce the amount of code it brings in.

Yeah - I wanted your series to kick-start the ambitious project 
of splitting up the mega-monolithic sched.h include file - 
without anyone noticing. Now my plan is busted.

Many good people scared away from this daunting project in the 
past one or two decades, but they were chicken!

> I'll go back to the drawing board. I'll pull the relevant code 
> from sysctl.h into auto_group.h, then I'll remove the include 
> in sched.h. Then I'll track down all the build failures from 
> the above :).

As long as a few common config combinations work fine I can help 
out with tracking down weird config failures and can also fix 
them - in fact I almost managed to fix your previous series when 
I noticed that include/sched/ is still included in sched.h. (the 
price I paid for not looking closely enough before applying the 
patches.)

Thanks,

	Ingo

      reply	other threads:[~2013-02-04 11:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-31 19:52 [PATCHv2 2/2] sched/rt: add a tuning knob to allow changing SCHED_RR timeslice Clark Williams
2013-02-03 11:10 ` Ingo Molnar
2013-02-03 18:57   ` Ingo Molnar
2013-02-04  2:03     ` Clark Williams
2013-02-04 11:01       ` Ingo Molnar [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=20130204110101.GC24173@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