All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [patch] mmap-speedup-2.5.42-C3
Date: 16 Oct 2002 11:16:57 +0200	[thread overview]
Message-ID: <m3u1jmpwty.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <20021016040754.C5659@devserv.devel.redhat.com>

Jakub Jelinek <jakub@redhat.com> writes:

You can argue against it, but it doesn't change the fact that 
get_unmapped_area is a significant user of CPU on a KDE startup. You
can do the oprofile yourself if you don't believe me. And where else should 
it come from other than from mapping shared libraries ?

This includes X server startup, but at least my X has a much shorter
/proc/*/maps than a KDE program, so I don't think X is a significant
consumer of vmas.

-Andi

  parent reply	other threads:[~2002-10-16  9:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-15 13:11 [patch] mmap-speedup-2.5.42-C3 Ingo Molnar
2002-10-15 13:11 ` Ingo Molnar
2002-10-15 18:09 ` Andrew Morton
2002-10-15 18:09   ` Andrew Morton
2002-10-15 21:30   ` Andi Kleen
2002-10-16  8:03     ` Ingo Molnar
2002-10-16  8:07       ` Jakub Jelinek
2002-10-16  8:27         ` Ingo Molnar
2002-10-16  8:22           ` Jakub Jelinek
2002-10-16  9:16         ` Andi Kleen [this message]
2002-10-16  9:47           ` Ingo Molnar
2002-10-16 12:08             ` Jakub Jelinek
2002-10-16  1:14 ` Saurabh Desai
2002-10-16  1:14   ` Saurabh Desai
2002-10-16  8:14   ` Ingo Molnar
2002-10-16  8:14     ` Ingo Molnar
2002-10-16 14:52     ` Linus Torvalds
2002-10-16 14:52       ` Linus Torvalds
2002-10-16 15:49       ` Arjan van de Ven
2002-10-16 16:10         ` Andrew Morton
2002-10-16 16:10           ` Andrew Morton

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=m3u1jmpwty.fsf@averell.firstfloor.org \
    --to=ak@muc.de \
    --cc=jakub@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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.