public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Clark Williams <williams@redhat.com>
To: Ingo Molnar <mingo@kernel.org>
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: Sun, 3 Feb 2013 20:03:16 -0600	[thread overview]
Message-ID: <20130203200316.63c15a79@riff.lan> (raw)
In-Reply-To: <20130203185709.GA22826@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]

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. 

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 :).

Clark

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2013-02-04  2:03 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 [this message]
2013-02-04 11:01       ` Ingo Molnar

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=20130203200316.63c15a79@riff.lan \
    --to=williams@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --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