From: Arjan van de Ven <arjan@infradead.org>
To: Andrew Morton <akpm@osdl.org>
Cc: davej@redhat.com, davem@davemloft.net, pmarques@grupopie.com,
linux-kernel@vger.kernel.org
Subject: Re: Slowdown with randomize_va_space in 2.6.12.2
Date: Thu, 07 Jul 2005 08:46:03 +0200 [thread overview]
Message-ID: <1120718764.3198.14.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20050706234102.2172ca76.akpm@osdl.org>
On Wed, 2005-07-06 at 23:41 -0700, Andrew Morton wrote:
> Arjan van de Ven <arjan@infradead.org> wrote:
> >
> > > > On Transmeta CPUs that probably triggers a retranslation of
> > > > x86->native bytecode, if it thinks it hasn't seen code at that
> > > > address before.
> > > >
> > >
> > > ouch. What do we do? Default to off? Default to off on xmeta?
> >
> > off-on-xmeta would be my preference; I'll cook up a patch for that.
>
> Well we seem to have several people reporting problems of various sorts
> with that patch?
actually we have several people reporting problems that started around
the time the patch got merged. There's very few cases that actually go
away when disabling this. (there's the weird kernel build one and we're
waiting on a good maps on that one)
next prev parent reply other threads:[~2005-07-07 6:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 14:23 Paulo Marques
2005-07-06 19:57 ` David S. Miller
2005-07-06 20:53 ` Dave Jones
2005-07-06 20:58 ` David S. Miller
2005-07-07 1:12 ` Andrew Morton
2005-07-07 2:07 ` David S. Miller
2005-07-07 4:11 ` pmarques
2005-07-07 6:37 ` Arjan van de Ven
2005-07-07 6:41 ` Andrew Morton
2005-07-07 6:46 ` Arjan van de Ven [this message]
2005-07-30 0:53 ` Eric Lammerts
2005-07-30 1:20 ` Andrew Morton
2005-07-30 11:49 ` Arjan van de Ven
2005-07-30 11:55 ` Arjan van de Ven
2005-07-06 21:00 ` Arjan van de Ven
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=1120718764.3198.14.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pmarques@grupopie.com \
/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
all inboxes | Powered by JetHome®