[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100915222216.GF27658@esdhcp04044.research.nokia.com>
Date: Thu, 16 Sep 2010 01:22:16 +0300
From: Phil Carmody <ext-phil.2.carmody@...ia.com>
To: ext Tony Luck <tony.luck@...el.com>
Cc: "fenghua.yu@...el.com" <fenghua.yu@...el.com>,
"linux-ia64@...r.kernel.org" <linux-ia64@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/2] ia64: possible module unwind table optimisation
On 15/09/10 19:28 +0200, ext Tony Luck wrote:
> On Wed, Sep 15, 2010 at 5:48 AM, Phil Carmody
> <ext-phil.2.carmody@...ia.com> wrote:
> >> for (table = unw.tables; table; table = table->next)
> >>
> >> before we find the right table to look?
> >
> > Yes, that's the one. Sorry I wasn't more explicit.
>
> My usual workload (building new Linux kernels - what else :-) doesn't
> seem to generate
> any unwind requests. I reached the loop just 58 times while booting,
> and only did 23
> steps past the first item [didn't track a histogram, so I don't know
> whether that was a
> single 23 step lookup, or 23 one-step ones]. Building the kernel
> (make -j32) didn't add
> to either count.
>
> Workload ideas?
Turn on kmemleak, or anything else which repeatedly runs up the stack just
for the fun of gathering backtraces. Kmemleak's what caused us to notice
the issue in our ARM-based environment.
Phil
--
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