linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.6.0-test3-mm1
Date: Mon, 11 Aug 2003 16:00:44 -0700	[thread overview]
Message-ID: <886340000.1060642844@flay> (raw)
In-Reply-To: <884580000.1060642229@flay>

>> On Mon, Aug 11, 2003 at 01:17:04PM -0700, Martin J. Bligh wrote:
>>> Buggered if I know what Letext is doing there ???
>>>       6577     3.9% total
>>>       1157     0.0% Letext
>>>        937     0.0% direct_strnlen_user
>>>        748   440.0% filp_close
>>>        722    21.2% __copy_from_user_ll
>>>        610     2.6% page_remove_rmap
>>>        492   487.1% file_ra_state_init
>>>        452    12.4% find_get_page
>>>        405     7.6% __copy_to_user_ll
>>>        402    28.6% schedule
>>>        386     0.0% kpmd_ctor
>>>        348     4.4% __d_lookup
>>>        310    16.6% atomic_dec_and_lock
>>>        300   174.4% may_open
>> 
>> You can figure out what it is by reading addresses directly out of
>> /proc/profile that would correspond to it (i.e. modifying readprofile)
>> and correlating it with an area of text in a disassembled kernel.
> 
> Was more interested in which patch screwed up the profiling really ...
> I suspect someone knows already ;-)

Looks to me like all the .text.lock.foo stuff got dumped under Letext
actually .... oops. Sometime between test2-mm1 and test2-mm3, I think?

M.

--
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:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2003-08-11 23:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-10  3:39 2.6.0-test3-mm1 Andrew Morton
2003-08-10 17:41 ` 2.6.0-test3-mm1 Thomas Schlichter
2003-08-11 18:26   ` 2.6.0-test3-mm1 George Anzinger
2003-08-13 20:18     ` 2.6.0-test3-mm1 Sam Ravnborg
2003-08-13 20:58       ` 2.6.0-test3-mm1 Martin J. Bligh
2003-08-14  8:17       ` 2.6.0-test3-mm1 and the -g thing George Anzinger
2003-08-11 14:03 ` 2.6.0-test3-mm1 Luiz Capitulino
2003-08-11 14:35 ` 2.6.0-test3-mm1 Martin J. Bligh
2003-08-11 15:17   ` 2.6.0-test3-mm1 Con Kolivas
2003-08-11 18:05   ` 2.6.0-test3-mm1 William Lee Irwin III
2003-08-11 18:57     ` 2.6.0-test3-mm1 Martin J. Bligh
2003-08-11 21:55     ` 2.6.0-test3-mm1 Con Kolivas
2003-08-11 22:19       ` 2.6.0-test3-mm1 William Lee Irwin III
2003-08-11 18:39   ` 2.6.0-test3-mm1 Andrew Morton
2003-08-11 20:17     ` 2.6.0-test3-mm1 Martin J. Bligh
2003-08-11 22:16       ` 2.6.0-test3-mm1 William Lee Irwin III
2003-08-11 22:50         ` 2.6.0-test3-mm1 Martin J. Bligh
2003-08-11 23:00           ` Martin J. Bligh [this message]
2003-08-11 23:39           ` 2.6.0-test3-mm1 William Lee Irwin III

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=886340000.1060642844@flay \
    --to=mbligh@aracnet.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=wli@holomorphy.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