From: Andy Whitcroft <apw@shadowen.org>
To: Martin Bligh <mbligh@mbligh.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Christoph Lameter <clameter@sgi.com>,
linux-mm@kvack.org, Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: SLUB: Use ilog2 instead of series of constant comparisons.
Date: Thu, 07 Jun 2007 08:40:06 +0100 [thread overview]
Message-ID: <4667B656.3080308@shadowen.org> (raw)
In-Reply-To: <46671C16.9080409@mbligh.org>
Martin Bligh wrote:
> Andrew Morton wrote:
>> On Wed, 6 Jun 2007 13:28:40 -0700 (PDT) Christoph Lameter
>> <clameter@sgi.com> wrote:
>>
>>> On Wed, 6 Jun 2007, Andrew Morton wrote:
>>>
>>>>> There is also nothing special in CalcNTLMv2_partial_mac_key(). Two
>>>>> kmallocs of 33 bytes and 132 bytes each.
>>>> Yes, the code all looks OK. I suspect this is another case of the
>>>> compiler
>>>> failing to remove unreachable stuff.
>>> Sigh.
>>>
>>> The patch was already in 2.6.22-rc3-mm1. Why did the patch pass the
>>> testing during that release cycle?
>>
>> Good question - don't know, sorry.
>>
>> I tried to build gcc-3.3.3 the other day. Would you believe that
>> gcc-4.1.0
>> fails to compile gcc-3.3.3?
>
> IIRC, the SUSE ones were customized anyway, so not sure that'd help you.
> Might do though.
>
> There should be a sysinfo directory that lists stuff like gcc version,
> maybe it's not getting replicated to TKO though ... Nish or Andy,
> any chance you can take a look at the original copy of one of those
> jobs on the ABAT server?
>
> I just fixed autotest, but I can't fix the old IBM code from here ;-)
> Anything else that'd be particularly handy to dump all the time?
> You can see what we're currently doing in the context of the diff
> below.
>
> Index: sysinfo.py
> ===================================================================
> --- sysinfo.py (revision 527)
> +++ sysinfo.py (working copy)
> @@ -8,7 +8,7 @@
> files = ['/proc/pci', '/proc/meminfo', '/proc/slabinfo', '/proc/version',
> '/proc/cpuinfo', '/proc/cmdline']
> # commands = ['lshw'] # this causes problems triggering CDROM
> drives
> -commands = ['uname -a', 'lspci -vvn']
> +commands = ['uname -a', 'lspci -vvn', 'gcc --version']
> path = ['/usr/bin', '/bin']
Yep this is something we keep in the job, but apparently something we
don't push out to you.
Reading specs from /usr/lib/gcc-lib/powerpc-suse-linux/3.3.3/specs
Configured with: ../configure --enable-threads=posix --prefix=/usr
--with-local-prefix=/usr/local --infodir=/usr/share/info
--mandir=/usr/share/man --enable-languages=c,c++,f77,objc,java,ada
--disable-checking --libdir=/usr/lib --enable-libgcj
--with-gxx-include-dir=/usr/include/g++ --with-slibdir=/lib
--with-system-zlib --enable-shared --enable-__cxa_atexit
--host=powerpc-suse-linux --build=powerpc-suse-linux
--target=powerpc-suse-linux --enable-targets=powerpc64-suse-linux
--enable-biarch
Thread model: posix
gcc version 3.3.3 (SuSE Linux)
-apw
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-06-07 7:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 19:51 Christoph Lameter
2007-05-22 8:45 ` Pekka Enberg
2007-06-06 17:08 ` Andrew Morton
2007-06-06 18:36 ` Christoph Lameter
2007-06-06 20:11 ` Andrew Morton
2007-06-06 20:28 ` Christoph Lameter
2007-06-06 20:34 ` Andrew Morton
2007-06-06 20:41 ` Martin Bligh
2007-06-06 20:52 ` Christoph Lameter
2007-06-06 23:19 ` Andrew Morton
2007-06-06 23:50 ` Christoph Lameter
2007-06-07 0:01 ` Nish Aravamudan
2007-06-07 3:49 ` Christoph Lameter
2007-06-06 23:31 ` Nish Aravamudan
2007-06-07 7:40 ` Andy Whitcroft [this message]
2007-06-06 20:43 ` Christoph Lameter
2007-06-06 20:29 ` Nish Aravamudan
2007-06-07 7:48 ` Andy Whitcroft
2007-06-07 7:58 ` Andy Whitcroft
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=4667B656.3080308@shadowen.org \
--to=apw@shadowen.org \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=linux-mm@kvack.org \
--cc=mbligh@mbligh.org \
--cc=penberg@cs.helsinki.fi \
/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