From: Andrea Arcangeli <aarcange@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Marcelo Tosatti <mtosatti@redhat.com>,
Adam Litke <agl@us.ibm.com>, Avi Kivity <avi@redhat.com>,
Izik Eidus <ieidus@redhat.com>,
Hugh Dickins <hugh.dickins@tiscali.co.uk>,
Nick Piggin <npiggin@suse.de>, Rik van Riel <riel@redhat.com>,
Mel Gorman <mel@csn.ul.ie>, Dave Hansen <dave@linux.vnet.ibm.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Mike Travis <travis@sgi.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Christoph Lameter <cl@linux-foundation.org>,
Chris Wright <chrisw@sous-sol.org>,
bpicco@redhat.com,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>,
Chris Mason <chris.mason@oracle.com>,
Borislav Petkov <bp@alien8.de>
Subject: Re: Transparent Hugepage Support #22
Date: Fri, 30 Apr 2010 19:00:37 +0200 [thread overview]
Message-ID: <20100430170037.GJ22108@random.random> (raw)
In-Reply-To: <20100430085427.GA11032@elte.hu>
On Fri, Apr 30, 2010 at 10:54:27AM +0200, Ingo Molnar wrote:
> It would be nice and informative to have two diffstats in the announcement:
>
> - an 'absolute' one that shows all the hugetlb changes relative to upstream
> (or relative to -mm, whichever tree you use as a base),
That's easy, I will do next times. I'm based on mainline right now.
> - and [if possible] a 'delta' one that shows the diffstat to the previous
> version you've announced. [say in this current case the #21..#22 delta
> diffstat] [this might not always be easy to provide, when the upstream base
> changes.]
I've revision control on the quilt patchset, I can send the diffstat
of the quilt patchset.
You can also monitor the changes by running:
git fetch
git diff origin/master
before "git checkout origin/master".
but as you said that will also show the new mainline changes mixed
with my changes.
> That way people can see the general direction and scope from the email,
> without having to fetch any of the trees.
It's informative yes, but I hope that people really fetch the tree,
review the changes with "git log -p" or just blind test it and run
some benchmark. Many already did and that is the only way to get
feedback (positive or negative) and to be sure that we're going into
the right direction. The only feedback I got so far from people
testing the tree has been exceedingly positive which in addition to
the benchmarks I run myself, makes me more confident this is going in
the right direction and helping a wider scope of workloads. The
research I did initially on the prefault logic I think helped me
keeping things simpler and more efficient and I think the decision
that it was worth it do larger copy-page/clear-page only if we also
get something more than a prefault speedup in return (as those copies
slowdown the page faults and trashes the cache) is paying off.
--
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>
prev parent reply other threads:[~2010-04-30 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 14:41 Transparent Hugepage Support #22 Andrea Arcangeli
2010-04-30 8:54 ` Ingo Molnar
2010-04-30 17:00 ` Andrea Arcangeli [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=20100430170037.GJ22108@random.random \
--to=aarcange@redhat.com \
--cc=agl@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=avi@redhat.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=bp@alien8.de \
--cc=bpicco@redhat.com \
--cc=chris.mason@oracle.com \
--cc=chrisw@sous-sol.org \
--cc=cl@linux-foundation.org \
--cc=dave@linux.vnet.ibm.com \
--cc=hannes@cmpxchg.org \
--cc=hugh.dickins@tiscali.co.uk \
--cc=ieidus@redhat.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=mingo@elte.hu \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=nishimura@mxp.nes.nec.co.jp \
--cc=npiggin@suse.de \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=travis@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).