From: "H. Peter Anvin" <hpa@linux.intel.com>
To: Andrea Arcangeli <aarcange@redhat.com>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, Andi Kleen <ak@linux.intel.com>,
linux-kernel@vger.kernel.org,
"Kirill A. Shutemov" <kirill@shutemov.name>,
Arnd Bergmann <arnd@arndb.de>, Ingo Molnar <mingo@kernel.org>,
linux-arch@vger.kernel.org
Subject: Re: [PATCH 0/3] Virtual huge zero page
Date: Mon, 01 Oct 2012 10:33:12 -0700 [thread overview]
Message-ID: <5069D3D8.9070805@linux.intel.com> (raw)
In-Reply-To: <20121001172624.GD18051@redhat.com>
On 10/01/2012 10:26 AM, Andrea Arcangeli wrote:
>
>> It is well known that microbenchmarks can be horribly misleading. What
>> led to Kirill investigating huge zero page in the first place was the
>> fact that some applications/macrobenchmarks benefit, and I think those
>> are the right thing to look at.
>
> The whole point of the two microbenchmarks was to measure the worst
> cases for both scenarios and I think that was useful. Real life using
> zero pages are going to be somewhere in that range.
>
... and I think it would be worthwhile to know which effect dominates
(or neither, in which case it doesn't matter).
Overall, I'm okay with either as long as we don't lock down 2 MB when
there isn't a huge zero page in use.
-hpa
WARNING: multiple messages have this Message-ID (diff)
From: "H. Peter Anvin" <hpa@linux.intel.com>
To: Andrea Arcangeli <aarcange@redhat.com>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, Andi Kleen <ak@linux.intel.com>,
linux-kernel@vger.kernel.org,
"Kirill A. Shutemov" <kirill@shutemov.name>,
Arnd Bergmann <arnd@arndb.de>, Ingo Molnar <mingo@kernel.org>,
linux-arch@vger.kernel.org
Subject: Re: [PATCH 0/3] Virtual huge zero page
Date: Mon, 01 Oct 2012 10:33:12 -0700 [thread overview]
Message-ID: <5069D3D8.9070805@linux.intel.com> (raw)
In-Reply-To: <20121001172624.GD18051@redhat.com>
On 10/01/2012 10:26 AM, Andrea Arcangeli wrote:
>
>> It is well known that microbenchmarks can be horribly misleading. What
>> led to Kirill investigating huge zero page in the first place was the
>> fact that some applications/macrobenchmarks benefit, and I think those
>> are the right thing to look at.
>
> The whole point of the two microbenchmarks was to measure the worst
> cases for both scenarios and I think that was useful. Real life using
> zero pages are going to be somewhere in that range.
>
... and I think it would be worthwhile to know which effect dominates
(or neither, in which case it doesn't matter).
Overall, I'm okay with either as long as we don't lock down 2 MB when
there isn't a huge zero page in use.
-hpa
--
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>
next prev parent reply other threads:[~2012-10-01 17:33 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-28 23:37 [PATCH 0/3] Virtual huge zero page Kirill A. Shutemov
2012-09-28 23:37 ` Kirill A. Shutemov
2012-09-28 23:37 ` [PATCH 1/3] asm-generic: introduce pmd_special() and pmd_mkspecial() Kirill A. Shutemov
2012-09-28 23:37 ` Kirill A. Shutemov
2012-09-28 23:37 ` [PATCH 2/3] mm, thp: implement virtual huge zero page Kirill A. Shutemov
2012-09-28 23:37 ` Kirill A. Shutemov
2012-09-28 23:37 ` [PATCH 3/3] x86: implement HAVE_PMD_SPECAIL Kirill A. Shutemov
2012-09-28 23:37 ` Kirill A. Shutemov
2012-09-29 13:48 ` [PATCH 0/3] Virtual huge zero page Andrea Arcangeli
2012-09-29 13:48 ` Andrea Arcangeli
2012-09-29 14:30 ` Andi Kleen
2012-09-29 14:30 ` Andi Kleen
2012-09-29 14:30 ` Andi Kleen
2012-09-29 14:37 ` Andrea Arcangeli
2012-09-29 14:37 ` Andrea Arcangeli
2012-10-01 13:49 ` Kirill A. Shutemov
2012-10-01 16:14 ` Andrea Arcangeli
2012-10-01 16:14 ` Andrea Arcangeli
2012-10-01 17:18 ` Kirill A. Shutemov
2012-10-01 17:18 ` Kirill A. Shutemov
2012-10-01 15:34 ` H. Peter Anvin
2012-10-01 15:34 ` H. Peter Anvin
2012-10-01 16:31 ` Andrea Arcangeli
2012-10-01 16:31 ` Andrea Arcangeli
2012-10-01 17:03 ` H. Peter Anvin
2012-10-01 17:03 ` H. Peter Anvin
2012-10-01 17:15 ` Kirill A. Shutemov
2012-10-01 17:15 ` Kirill A. Shutemov
2012-10-01 18:03 ` Andrea Arcangeli
2012-10-01 18:03 ` Andrea Arcangeli
2012-10-01 17:26 ` Andrea Arcangeli
2012-10-01 17:26 ` Andrea Arcangeli
2012-10-01 17:33 ` H. Peter Anvin [this message]
2012-10-01 17:33 ` H. Peter Anvin
2012-10-01 17:36 ` Kirill A. Shutemov
2012-10-01 17:36 ` Kirill A. Shutemov
2012-10-01 17:37 ` H. Peter Anvin
2012-10-01 17:37 ` H. Peter Anvin
2012-10-01 17:44 ` Kirill A. Shutemov
2012-10-01 17:44 ` Kirill A. Shutemov
2012-10-01 17:52 ` H. Peter Anvin
2012-10-01 17:52 ` H. Peter Anvin
2012-10-01 18:56 ` Kirill A. Shutemov
2012-10-01 18:56 ` Kirill A. Shutemov
2012-10-01 18:05 ` Andrea Arcangeli
2012-10-01 18:05 ` Andrea Arcangeli
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=5069D3D8.9070805@linux.intel.com \
--to=hpa@linux.intel.com \
--cc=aarcange@redhat.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@kernel.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.