All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: Arjan van de Ven <arjan@linux.intel.com>,
	linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
	Val Henson <val.henson@intel.com>
Subject: Re: [patch 00/14] remap_file_pages protection support
Date: Tue, 02 May 2006 18:44:48 -0700	[thread overview]
Message-ID: <44580B10.2000205@redhat.com> (raw)
In-Reply-To: <200605030226.28047.blaisorblade@yahoo.it>

[-- Attachment #1: Type: text/plain, Size: 964 bytes --]

Blaisorblade wrote:
>> I've not seen much of this if any at all, the various caches that are in
>> place for these lookups seem to function quite well; what we did see was
>> glibc's malloc implementation being mistuned resulting in far too many
>> mmaps than needed (which in turn leads to far too much page zeroing
>> which is the really expensive part. It's not the vma lookup that is
>> expensive, it's the page zeroing)
> Even to this email, I hope Ulrich will answer.

All I can say is that some of our guys tuning a big application on a
customer's site reported seeing the VMA lookups being on the profile
list.  This was some huge Java program.  It might be that every other
page had a different protection, executable or not, read-only mmap etc.
 And data access for very non-local.

I cannot say more since this was near to the end of the trials.

-- 
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]

      reply	other threads:[~2006-05-03  1:45 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-30 17:29 [patch 00/14] remap_file_pages protection support blaisorblade
2006-04-30 17:29 ` [patch 01/14] Fix comment about remap_file_pages blaisorblade
2006-04-30 17:29 ` [patch 02/14] remap_file_pages protection support: add needed macros blaisorblade
2006-04-30 17:29 ` [patch 03/14] remap_file_pages protection support: handle MANYPROTS VMAs blaisorblade
2006-04-30 17:29 ` [patch 04/14] remap_file_pages protection support: disallow mprotect() on manyprots mappings blaisorblade
2006-04-30 17:29 ` [patch 05/14] remap_file_pages protection support: cleanup syscall checks blaisorblade
2006-04-30 17:29 ` [patch 06/14] remap_file_pages protection support: enhance syscall interface blaisorblade
2006-04-30 17:30 ` [patch 07/14] remap_file_pages protection support: support private vma for MAP_POPULATE blaisorblade
2006-04-30 17:30 ` [patch 08/14] remap_file_pages protection support: use FAULT_SIGSEGV for protection checking blaisorblade
2006-04-30 17:30 ` [patch 09/14] remap_file_pages protection support: fix race condition with concurrent faults on same address space blaisorblade
2006-04-30 17:30 ` [patch 10/14] remap_file_pages protection support: fix get_user_pages() on VM_MANYPROTS vmas blaisorblade
2006-04-30 17:30 ` [patch 11/14] remap_file_pages protection support: pte_present should not trigger on PTE_FILE PROTNONE ptes blaisorblade
2006-05-02  3:53   ` Nick Piggin
2006-05-02  3:53     ` Nick Piggin
2006-05-03  1:29     ` Blaisorblade
2006-05-03  1:29       ` Blaisorblade
2006-05-06 10:03       ` Nick Piggin
2006-05-06 10:03         ` Nick Piggin
2006-05-07 17:50         ` Blaisorblade
2006-05-07 17:50           ` Blaisorblade
2006-04-30 17:30 ` [patch 12/14] remap_file_pages protection support: also set VM_NONLINEAR on nonuniform VMAs blaisorblade
2006-04-30 17:30 ` [patch 13/14] remap_file_pages protection support: uml, i386, x64 bits blaisorblade
2006-04-30 17:30 ` [patch 14/14] remap_file_pages protection support: adapt to uml peculiarities blaisorblade
2006-05-02  3:45 ` [patch 00/14] remap_file_pages protection support Nick Piggin
2006-05-02  3:45   ` Nick Piggin
2006-05-02  3:56   ` Nick Piggin
2006-05-02  3:56     ` Nick Piggin
2006-05-02 11:24     ` Ingo Molnar
2006-05-02 11:24       ` Ingo Molnar
2006-05-02 12:19       ` Nick Piggin
2006-05-02 12:19         ` Nick Piggin
2006-05-02 17:16   ` Lee Schermerhorn
2006-05-02 17:16     ` Lee Schermerhorn
2006-05-03  1:20     ` Blaisorblade
2006-05-03  1:20       ` Blaisorblade
2006-05-03 14:35       ` Lee Schermerhorn
2006-05-03 14:35         ` Lee Schermerhorn
2006-05-03  0:25   ` Blaisorblade
2006-05-03  0:25     ` Blaisorblade
2006-05-06 16:05     ` Ulrich Drepper
2006-05-07  4:22       ` Nick Piggin
2006-05-07  4:22         ` Nick Piggin
2006-05-13 14:13         ` Nick Piggin
2006-05-13 18:19           ` Valerie Henson
2006-05-13 18:19             ` Valerie Henson
2006-05-13 22:54             ` Valerie Henson
2006-05-13 22:54               ` Valerie Henson
2006-05-16 13:30             ` Nick Piggin
2006-05-16 13:30               ` Nick Piggin
2006-05-16 13:51               ` Andreas Mohr
2006-05-16 13:51                 ` Andreas Mohr
2006-05-16 16:31                 ` Valerie Henson
2006-05-16 16:31                   ` Valerie Henson
2006-05-16 16:47                   ` Andreas Mohr
2006-05-16 16:47                     ` Andreas Mohr
2006-05-17  3:25                     ` Nick Piggin
2006-05-17  3:25                       ` Nick Piggin
2006-05-17  6:10                     ` Blaisorblade
2006-05-17  6:10                       ` Blaisorblade
2006-05-16 16:33               ` Valerie Henson
2006-05-16 16:33                 ` Valerie Henson
2006-05-03  0:44   ` Blaisorblade
2006-05-03  0:44     ` Blaisorblade
2006-05-06  9:06     ` Nick Piggin
2006-05-06  9:06       ` Nick Piggin
2006-05-06 15:26       ` Ulrich Drepper
2006-05-02 10:21 ` Arjan van de Ven
2006-05-02 23:46   ` Valerie Henson
2006-05-03  0:26   ` Blaisorblade
2006-05-03  1:44     ` Ulrich Drepper [this message]

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=44580B10.2000205@redhat.com \
    --to=drepper@redhat.com \
    --cc=akpm@osdl.org \
    --cc=arjan@linux.intel.com \
    --cc=blaisorblade@yahoo.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=val.henson@intel.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 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.