Re: [PATCH] mm: remove global locks from mm/highmem.c

On Sun, Jan 28, 2007 at 04:17:00PM +0100, Ingo Molnar wrote:
> scalability. I did lock profiling on the -rt kernel, which exposes such 
> things nicely. Half of the lock contention events during kernel compile 
> were due to kmap(). (The system had 2 GB of RAM, so 40% lowmem, 60% 
> highmem.)

Numbers please, and not on -rt but on mainline.  Please show the profiles.

> ps. please fix your mailer to not emit Mail-Followup-To headers. In Mutt
>     you can do this via "set followup_to=no" in your .muttrc.

I have told you last time that this is absolutely intentional and I won't
change it.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH] mm: remove global locks from mm/highmem.c
    • From: Ingo Molnar <[email protected]>

• References:
  • [PATCH] mm: remove global locks from mm/highmem.c
    • From: Peter Zijlstra <[email protected]>
  • Re: [PATCH] mm: remove global locks from mm/highmem.c
    • From: Christoph Hellwig <[email protected]>
  • Re: [PATCH] mm: remove global locks from mm/highmem.c
    • From: Ingo Molnar <[email protected]>

• Prev by Date: Re: [PATCH 1/3] lutimesat: simplify utime(2)
• Next by Date: Re: [PATCH 0/7] breaking the global file_list_lock
• Previous by thread: Re: [PATCH] mm: remove global locks from mm/highmem.c
• Next by thread: Re: [PATCH] mm: remove global locks from mm/highmem.c
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]