From: Anton Starikov <ant.starikov@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [Bugme-new] [Bug 15618] New: 2.6.18->2.6.32->2.6.33 huge regression in performance
Date: Tue, 23 Mar 2010 19:19:22 +0100 [thread overview]
Message-ID: <1BAC48C3-2AF2-4FA2-9762-85727068BF64@gmail.com> (raw)
In-Reply-To: <20100323111351.756c8752.akpm@linux-foundation.org>
On Mar 23, 2010, at 7:13 PM, Andrew Morton wrote:
> Anton, we have an executable binary in the bugzilla report but it would
> be nice to also have at least a description of what that code is
> actually doing. A quick strace shows quite a lot of mprotect activity.
> A pseudo-code walkthrough, perhaps?
Right now can't say too much about the code (we just gave a chance to neighbor group to run their code on our cluster, so I'm totally unfriendly with this code). I will forward your question to them.
But probably right now you can get more information (including sources) here http://fmt.cs.utwente.nl/tools/ltsmin/
Anton
WARNING: multiple messages have this Message-ID (diff)
From: Anton Starikov <ant.starikov@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [Bugme-new] [Bug 15618] New: 2.6.18->2.6.32->2.6.33 huge regression in performance
Date: Tue, 23 Mar 2010 19:19:22 +0100 [thread overview]
Message-ID: <1BAC48C3-2AF2-4FA2-9762-85727068BF64@gmail.com> (raw)
In-Reply-To: <20100323111351.756c8752.akpm@linux-foundation.org>
On Mar 23, 2010, at 7:13 PM, Andrew Morton wrote:
> Anton, we have an executable binary in the bugzilla report but it would
> be nice to also have at least a description of what that code is
> actually doing. A quick strace shows quite a lot of mprotect activity.
> A pseudo-code walkthrough, perhaps?
Right now can't say too much about the code (we just gave a chance to neighbor group to run their code on our cluster, so I'm totally unfriendly with this code). I will forward your question to them.
But probably right now you can get more information (including sources) here http://fmt.cs.utwente.nl/tools/ltsmin/
Anton
--
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:[~2010-03-23 18:26 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-15618-10286@https.bugzilla.kernel.org/>
2010-03-23 14:22 ` [Bugme-new] [Bug 15618] New: 2.6.18->2.6.32->2.6.33 huge regression in performance Andrew Morton
2010-03-23 14:22 ` Andrew Morton
2010-03-23 17:34 ` Ingo Molnar
2010-03-23 17:34 ` Ingo Molnar
2010-03-23 17:45 ` Linus Torvalds
2010-03-23 17:45 ` Linus Torvalds
2010-03-23 17:57 ` Anton Starikov
2010-03-23 17:57 ` Anton Starikov
2010-03-23 18:00 ` Ingo Molnar
2010-03-23 18:00 ` Ingo Molnar
2010-03-23 18:03 ` Anton Starikov
2010-03-23 18:03 ` Anton Starikov
2010-03-23 18:21 ` Andrew Morton
2010-03-23 18:21 ` Andrew Morton
2010-03-23 18:25 ` Anton Starikov
2010-03-23 18:25 ` Anton Starikov
2010-03-23 19:22 ` Robin Holt
2010-03-23 19:22 ` Robin Holt
2010-03-23 19:30 ` Anton Starikov
2010-03-23 19:30 ` Anton Starikov
2010-03-23 19:49 ` Robin Holt
2010-03-23 19:49 ` Robin Holt
2010-03-23 19:57 ` Robin Holt
2010-03-23 19:57 ` Robin Holt
2010-03-23 19:50 ` Anton Starikov
2010-03-23 19:50 ` Anton Starikov
2010-03-23 19:52 ` Linus Torvalds
2010-03-23 19:52 ` Linus Torvalds
2010-03-24 16:40 ` Roland Dreier
2010-03-24 16:40 ` Roland Dreier
2010-03-26 3:24 ` Anton Starikov
2010-03-26 3:24 ` Anton Starikov
2010-03-23 19:14 ` Anton Starikov
2010-03-23 19:14 ` Anton Starikov
2010-03-23 19:17 ` Peter Zijlstra
2010-03-23 19:17 ` Peter Zijlstra
2010-03-23 19:42 ` Anton Starikov
2010-03-23 19:54 ` Linus Torvalds
2010-03-23 19:54 ` Linus Torvalds
2010-03-23 20:43 ` Anton Starikov
2010-03-23 20:43 ` Anton Starikov
2010-03-23 23:04 ` Linus Torvalds
2010-03-23 23:04 ` Linus Torvalds
2010-03-23 23:19 ` Anton Starikov
2010-03-23 23:19 ` Anton Starikov
2010-03-23 23:36 ` Ingo Molnar
2010-03-23 23:36 ` Ingo Molnar
2010-03-23 23:55 ` Linus Torvalds
2010-03-23 23:55 ` Linus Torvalds
2010-03-24 0:03 ` Anton Starikov
2010-03-24 0:03 ` Anton Starikov
2010-03-24 2:15 ` Andi Kleen
2010-03-24 2:15 ` Andi Kleen
2010-03-24 3:00 ` Linus Torvalds
2010-03-24 3:00 ` Linus Torvalds
2010-04-19 18:19 ` Greg KH
2010-04-19 18:19 ` Greg KH
2010-03-23 18:13 ` Andrew Morton
2010-03-23 18:13 ` Andrew Morton
2010-03-23 18:19 ` Anton Starikov [this message]
2010-03-23 18:19 ` Anton Starikov
2010-03-23 18:27 ` Ingo Molnar
2010-03-23 18:27 ` Ingo Molnar
2010-03-23 21:19 ` Anton Starikov
2010-03-23 21:19 ` Anton Starikov
2010-04-02 18:57 ` Lee Schermerhorn
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=1BAC48C3-2AF2-4FA2-9762-85727068BF64@gmail.com \
--to=ant.starikov@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.org \
/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.