mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Thomas Gleixner <tglx@linutronix.de>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Paul Gortmaker <paul.gortmaker@windriver.com>
Subject: [PATCHv2 0/2] sched: move content out of core files for load calculations
Date: Fri, 19 Apr 2013 15:10:48 -0400	[thread overview]
Message-ID: <1366398650-31599-1-git-send-email-paul.gortmaker@windriver.com> (raw)

Recent activity has had a focus on moving functionally related blocks of
stuff out of sched/core.c into stand-alone files.  The code relating to load
calculations has grown significantly enough recently to warrant placing it in
a separate file.

Here we do that, and in doing so, we shed ~20k of code from sched/core.c (~10%).

A couple small static functions in the core sched.h header were also localized
to their singular user in sched/fair.c at the same time, with the goal to also
reduce the amount of "broadcast" content in that sched.h file.

Paul.
---

v2 changes:

  1) rebase from tip's sched/core (v3.9-rc1-38-gb329fd5) to today's
     tip master (v3.9-rc6-2031-g27f8b76).
  2) rename file from load_avg.c to proc.c

---

The following changes since commit 27f8b769cba5a97ffcbaae92fd4c0ed84f00e214:

  manual merge of tools/kvm (2013-04-19 13:05:17 +0200)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux.git for-ingo

for you to fetch changes up to dac25445169ff97142ae4f7174e3d94ce7036ad3:

  sched: move update_load_[add/sub/set] from sched.h to fair.c (2013-04-19 14:38:11 -0400)

----------------------------------------------------------------
Paul Gortmaker (2):
      sched: fork load calculation code from sched/core --> sched/proc
      sched: move update_load_[add/sub/set] from sched.h to fair.c

 kernel/sched/Makefile |   2 +-
 kernel/sched/core.c   | 569 -------------------------------------------------
 kernel/sched/fair.c   |  18 ++
 kernel/sched/proc.c   | 578 ++++++++++++++++++++++++++++++++++++++++++++++++++
 kernel/sched/sched.h  |  26 +--
 5 files changed, 605 insertions(+), 588 deletions(-)
 create mode 100644 kernel/sched/proc.c

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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-19 19:10 Paul Gortmaker [this message]
2013-04-19 19:10 ` [PATCHv2 1/2] sched: fork load calculation code from sched/core --> sched/proc Paul Gortmaker
2013-05-07 14:10   ` [tip:sched/urgent] sched: Factor out load calculation code from sched/core.c --> sched/proc.c tip-bot for Paul Gortmaker
2013-04-19 19:10 ` [PATCHv2 2/2] sched: move update_load_[add/sub/set] from sched.h to fair.c Paul Gortmaker
2013-05-07 14:12   ` [tip:sched/urgent] sched: Move update_load_*() methods " tip-bot for Paul Gortmaker
2013-04-21  9:18 ` [PATCHv2 0/2] sched: move content out of core files for load calculations Ingo Molnar
2013-05-06  9:26   ` Ingo Molnar
2013-05-06 14:21     ` Paul Gortmaker

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=1366398650-31599-1-git-send-email-paul.gortmaker@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.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

Powered by JetHome