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]
Message-ID: <20110211135906.GA16358@elte.hu>
Date:	Fri, 11 Feb 2011 14:59:06 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	linux-arch@...r.kernel.org, Greg Kroah-Hartman <gregkh@...e.de>
Subject: Re: [patch 00/75] genirq: Overhaul for 2.6.39


* Thomas Gleixner <tglx@...utronix.de> wrote:

> B1;2401;0cOn Fri, 11 Feb 2011, Thomas Gleixner wrote:
> > On Thu, 10 Feb 2011, Linus Torvalds wrote:
> > So yes, it's net more source lines, but not resulting in any binary
> > bloat.
> 
> Just checked. When the compat layer goes away it will kill about 500
> lines. So it's less code with better encapsulation.
> 
> Once all genirq archs convert to the generic irq_show_interrupts(),
> this will kill another 1000+ lines.

So while this is the first step:

>  29 files changed, 1353 insertions(+), 899 deletions(-)

It turns into this end result (mockup):

>  129 files changed, 1353 insertions(+), 2400 deletions(-)

Right? Or, more likely, considering all the surrounding code changes, something 
like:

>  129 files changed, 4353 insertions(+), 5400 deletions(-)

Did I get the file count right - roughtly how many files are affected throughout all 
architectures? The changes are massively intrusive and widely spread out so we 
cannot do them in one go, right?

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