lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 6 May 2013 11:26:58 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Paul Gortmaker <paul.gortmaker@...driver.com>
Cc:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Thomas Gleixner <tglx@...utronix.de>,
	Frederic Weisbecker <fweisbec@...il.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCHv2 0/2] sched: move content out of core files for load
 calculations


* Ingo Molnar <mingo@...nel.org> wrote:

> 
> * Paul Gortmaker <paul.gortmaker@...driver.com> wrote:
> 
> > 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
> 
> Thanks, looks good to me. Note, I'll try to apply this after the initial 
> round of trees went to Linus in the merge window, to reduce interactions 
> between the trees. [...]

Ok, all relevant trees are now upstream - mind sending a refreshed series 
against upstream merge commit 534c97b0950b or later?

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ