From: Rasmus Villemoes <linux@rasmusvillemoes.dk>
To: Ingo Molnar <mingo@kernel.org>
Cc: George Spelvin <linux@horizon.com>,
dave@sr71.net, linux-kernel@vger.kernel.org, linux-mm@kvack.org,
peterz@infradead.org, riel@redhat.com, rientjes@google.com,
torvalds@linux-foundation.org
Subject: Re: [PATCH 3/3 v3] mm/vmalloc: Cache the vmalloc memory info
Date: Mon, 24 Aug 2015 10:39:17 +0200 [thread overview]
Message-ID: <877fol5bd6.fsf@rasmusvillemoes.dk> (raw)
In-Reply-To: <20150824065809.GA13082@gmail.com> (Ingo Molnar's message of "Mon, 24 Aug 2015 08:58:09 +0200")
On Mon, Aug 24 2015, Ingo Molnar <mingo@kernel.org> wrote:
>
> Thanks, is the fixed up changelog below better?
>
Yes, though Linus specifically referred to "make test" (but I guess one
could/should consider that part of the build process).
Rasmus
> mm/vmalloc: Cache the vmalloc memory info
>
> Linus reported that for scripting-intense workloads such as the
> Git build, glibc's qsort will read /proc/meminfo for every process
> created (by way of get_phys_pages()), which causes the Git build
> to generate a surprising amount of kernel overhead.
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Rasmus Villemoes <linux@rasmusvillemoes.dk>
To: Ingo Molnar <mingo@kernel.org>
Cc: George Spelvin <linux@horizon.com>,
dave@sr71.net, linux-kernel@vger.kernel.org, linux-mm@kvack.org,
peterz@infradead.org, riel@redhat.com, rientjes@google.com,
torvalds@linux-foundation.org
Subject: Re: [PATCH 3/3 v3] mm/vmalloc: Cache the vmalloc memory info
Date: Mon, 24 Aug 2015 10:39:17 +0200 [thread overview]
Message-ID: <877fol5bd6.fsf@rasmusvillemoes.dk> (raw)
In-Reply-To: <20150824065809.GA13082@gmail.com> (Ingo Molnar's message of "Mon, 24 Aug 2015 08:58:09 +0200")
On Mon, Aug 24 2015, Ingo Molnar <mingo@kernel.org> wrote:
>
> Thanks, is the fixed up changelog below better?
>
Yes, though Linus specifically referred to "make test" (but I guess one
could/should consider that part of the build process).
Rasmus
> mm/vmalloc: Cache the vmalloc memory info
>
> Linus reported that for scripting-intense workloads such as the
> Git build, glibc's qsort will read /proc/meminfo for every process
> created (by way of get_phys_pages()), which causes the Git build
> to generate a surprising amount of kernel overhead.
next prev parent reply other threads:[~2015-08-24 8:39 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-23 4:48 [PATCH 0/3] mm/vmalloc: Cache the /proc/meminfo vmalloc statistics George Spelvin
2015-08-23 4:48 ` George Spelvin
2015-08-23 6:04 ` Ingo Molnar
2015-08-23 6:04 ` Ingo Molnar
2015-08-23 6:46 ` George Spelvin
2015-08-23 6:46 ` George Spelvin
2015-08-23 8:17 ` [PATCH 3/3 v3] mm/vmalloc: Cache the vmalloc memory info Ingo Molnar
2015-08-23 8:17 ` Ingo Molnar
2015-08-23 20:53 ` Rasmus Villemoes
2015-08-23 20:53 ` Rasmus Villemoes
2015-08-24 6:58 ` Ingo Molnar
2015-08-24 6:58 ` Ingo Molnar
2015-08-24 8:39 ` Rasmus Villemoes [this message]
2015-08-24 8:39 ` Rasmus Villemoes
2015-08-23 21:56 ` Rasmus Villemoes
2015-08-23 21:56 ` Rasmus Villemoes
2015-08-24 7:00 ` Ingo Molnar
2015-08-24 7:00 ` Ingo Molnar
2015-08-25 16:39 ` Linus Torvalds
2015-08-25 16:39 ` Linus Torvalds
2015-08-25 17:03 ` Linus Torvalds
2015-08-25 17:03 ` Linus Torvalds
2015-08-24 1:04 ` George Spelvin
2015-08-24 1:04 ` George Spelvin
2015-08-24 7:34 ` [PATCH 3/3 v4] " Ingo Molnar
2015-08-24 7:34 ` Ingo Molnar
2015-08-24 7:47 ` Ingo Molnar
2015-08-24 7:47 ` Ingo Molnar
2015-08-24 7:50 ` [PATCH 3/3 v5] " Ingo Molnar
2015-08-24 7:50 ` Ingo Molnar
2015-08-24 12:54 ` George Spelvin
2015-08-24 12:54 ` George Spelvin
2015-08-25 9:56 ` [PATCH 3/3 v6] " Ingo Molnar
2015-08-25 9:56 ` Ingo Molnar
2015-08-25 10:36 ` George Spelvin
2015-08-25 10:36 ` George Spelvin
2015-08-25 12:59 ` Peter Zijlstra
2015-08-25 12:59 ` Peter Zijlstra
2015-08-25 14:19 ` Rasmus Villemoes
2015-08-25 14:19 ` Rasmus Villemoes
2015-08-25 15:11 ` George Spelvin
2015-08-25 15:11 ` George Spelvin
2015-08-24 13:11 ` [PATCH 3/3 v4] " John Stoffel
2015-08-24 13:11 ` John Stoffel
2015-08-24 15:11 ` George Spelvin
2015-08-24 15:11 ` George Spelvin
2015-08-24 15:55 ` John Stoffel
2015-08-24 15:55 ` John Stoffel
2015-08-25 12:46 ` [PATCH 3/3 v3] " Peter Zijlstra
2015-08-25 12:46 ` Peter Zijlstra
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=877fol5bd6.fsf@rasmusvillemoes.dk \
--to=linux@rasmusvillemoes.dk \
--cc=dave@sr71.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@horizon.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=rientjes@google.com \
--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.