All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li Zefan <lizefan@huawei.com>
To: Clark Williams <williams@redhat.com>
Cc: Ingo Molnar <mingo@kernel.org>,
	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: [PATCH 1/2] sched: move scheduler sysctl bits into dedicated header file
Date: Tue, 29 Jan 2013 09:12:45 +0800	[thread overview]
Message-ID: <5107220D.6000606@huawei.com> (raw)
In-Reply-To: <20130128143120.1b60bfb6@redhat.com>

> -extern void sched_autogroup_create_attach(struct task_struct *p);
> -extern void sched_autogroup_detach(struct task_struct *p);
> -extern void sched_autogroup_fork(struct signal_struct *sig);
> -extern void sched_autogroup_exit(struct signal_struct *sig);
> -#ifdef CONFIG_PROC_FS
> -extern void proc_sched_autogroup_show_task(struct task_struct *p, struct seq_file *m);
> -extern int proc_sched_autogroup_set_nice(struct task_struct *p, int nice);
> -#endif
> -#else
> -static inline void sched_autogroup_create_attach(struct task_struct *p) { }
> -static inline void sched_autogroup_detach(struct task_struct *p) { }
> -static inline void sched_autogroup_fork(struct signal_struct *sig) { }
> -static inline void sched_autogroup_exit(struct signal_struct *sig) { }
> -#endif

but those function declarations have nothing to do with sysctl..

> -
> -#ifdef CONFIG_CFS_BANDWIDTH
> -extern unsigned int sysctl_sched_cfs_bandwidth_slice;
> -#endif
> -


  reply	other threads:[~2013-01-29  1:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-28 20:31 [PATCH 1/2] sched: move scheduler sysctl bits into dedicated header file Clark Williams
2013-01-29  1:12 ` Li Zefan [this message]
2013-01-29 17:55   ` Clark Williams
2013-01-29  6:05 ` Namhyung Kim
2013-01-29 17:57   ` Clark Williams
2013-01-29 18:05     ` Steven Rostedt
2013-01-31 11:25     ` 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=5107220D.6000606@huawei.com \
    --to=lizefan@huawei.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 \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.