From: Michael Riepe <michael.riepe@googlemail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org, oleg@redhat.com,
peterz@infradead.org, roland@redhat.com, efault@gmx.de,
rjw@sisk.pl, jdike@addtoit.com,
user-mode-linux-devel@lists.sourceforge.net,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
stable@kernel.org
Subject: Re: [patch] fix ptrace slowness
Date: Mon, 23 Mar 2009 20:08:21 +0100 [thread overview]
Message-ID: <49C7DE25.4030706@googlemail.com> (raw)
In-Reply-To: <E1Llmpk-0001A3-2E@pomaz-ex.szeredi.hu>
Hi!
Miklos Szeredi wrote:
> On Mon, 23 Mar 2009, Ingo Molnar wrote:
>
>>* Miklos Szeredi <miklos@szeredi.hu> wrote:
>>
>>
>>>This one incorporates comments from Oleg and Ingo. Please apply
>>>to 2.6.29 and 2.6.2[78]-stable trees.
>>
>>The fix first needs to go upstream. There's an alternative patch
>>below. Would you mind to give it a test? Chances are that it will
>>make UML even faster than your fix.
>
>
> Just the opposite. With my patch a UML image boots in 17 seconnds,
> with your patch it boots in 33 seconds. Without either patch it boots
> in about 5 minutes.
My strace test case runs 60% faster with this patch (compared to Ingo's).
--
Michael "Tired" Riepe <michael.riepe@googlemail.com>
X-Tired: Each morning I get up I die a little
next prev parent reply other threads:[~2009-03-23 19:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 15:07 [patch] fix ptrace slowness Miklos Szeredi
2009-03-23 15:19 ` Ingo Molnar
2009-03-23 15:53 ` Oleg Nesterov
2009-03-23 16:13 ` Ingo Molnar
2009-03-23 16:17 ` Miklos Szeredi
2009-03-23 16:38 ` Ingo Molnar
2009-03-23 19:08 ` Michael Riepe [this message]
2009-03-23 16:39 ` [tip:sched/urgent] sched, ptrace: fix UML and " Miklos Szeredi
2009-03-23 17:14 ` Ingo Molnar
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=49C7DE25.4030706@googlemail.com \
--to=michael.riepe@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=efault@gmx.de \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rjw@sisk.pl \
--cc=roland@redhat.com \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.