[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1240583100.29485.5.camel@nimitz>
Date: Fri, 24 Apr 2009 07:25:00 -0700
From: Dave Hansen <dave@...ux.vnet.ibm.com>
To: Mel Gorman <mel@....ul.ie>
Cc: Linux Memory Management List <linux-mm@...ck.org>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
Christoph Lameter <cl@...ux-foundation.org>,
Nick Piggin <npiggin@...e.de>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Lin Ming <ming.m.lin@...el.com>,
Zhang Yanmin <yanmin_zhang@...ux.intel.com>,
Peter Zijlstra <peterz@...radead.org>,
Pekka Enberg <penberg@...helsinki.fi>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 02/22] Do not sanity check order in the fast path
On Fri, 2009-04-24 at 10:21 +0100, Mel Gorman wrote:
> > dave@...nel:~/work/mhp-build$ ../linux-2.6.git/scripts/bloat-o-meter
> > i386-numaq-sparse.{1,2}/vmlinux
> > add/remove: 0/0 grow/shrink: 9/16 up/down: 81/-99 (-18)
> > function old new delta
> > st_int_ioctl 2600 2624 +24
> > tcp_sendmsg 2153 2169 +16
> > diskstats_show 739 753 +14
> > iov_shorten 49 58 +9
> > unmap_vmas 1653 1661 +8
> > sg_build_indirect 449 455 +6
> > ahc_linux_biosparam 251 253 +2
> > nlmclnt_call 557 558 +1
> > do_mount 1533 1534 +1
>
> It doesn't make sense at all that text increased in size. Did you make clean
> between each .config change and patch application? Are you using distcc
> or anything else that might cause confusion? I found I had to eliminate
> distscc and clean after each patch application because sometimes
> net/ipv4/udp.c would sometimes generate different assembly when
> accessing struct zone. Not really sure what was going on there.
There's a ccache in there but no distcc.
I'll redo with clean builds.
-- Dave
--
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