From: Hugh Dickins <hugh@veritas.com>
To: Jay Lan <jlan@engr.sgi.com>
Cc: David Wright <daw@sgi.com>,
Frank van Maarseveen <frankvm@frankvm.com>,
Christoph Lameter <clameter@engr.sgi.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.14-rc2] fix incorrect mm->hiwater_vm and mm->hiwater_rss
Date: Fri, 7 Oct 2005 04:03:30 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.61.0510070354590.16857@goblin.wat.veritas.com> (raw)
In-Reply-To: <4345D8DB.7070901@engr.sgi.com>
On Thu, 6 Oct 2005, Jay Lan wrote:
> Jay Lan wrote:
> > Hugh Dickins wrote:
> > >
> > > See comment in fs/proc/task_mmu.c for the principle. Could maintain
> > > hiwater_vm straightforwardly, but I think it's easier to remember if
> > > we handle them both in the same way.
> >
> > I am building a kernel with your patch and am going to run some test
> > to compare the statistics.
>
> My testing showed the same number on hiwater_vm, but hiwater_rss from
> Hugh's version was consistently ~1.5% lower. Where was the loss?
Thanks for trying it out. Please check if you adjusted the way in which
you collect hiwater_rss: as in the example in task_mmu.c, it's no longer
any good just reading hiwater_rss, you need the max of get_mm_rss and
hiwater_rss each time. Similarly for hiwater_vm.
Hugh
prev parent reply other threads:[~2005-10-07 3:04 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 12:19 Frank van Maarseveen
2005-09-21 14:38 ` Hugh Dickins
2005-09-21 14:58 ` Frank van Maarseveen
2005-09-21 15:35 ` Hugh Dickins
2005-09-21 18:42 ` Frank van Maarseveen
2005-09-21 18:57 ` Hugh Dickins
2005-09-21 15:26 ` Christoph Lameter
2005-09-21 15:50 ` Frank van Maarseveen
2005-09-21 16:57 ` Jay Lan
2005-09-21 17:05 ` Christoph Lameter
2005-09-21 17:39 ` Jay Lan
2005-09-21 18:06 ` Frank van Maarseveen
2005-09-21 18:38 ` Jay Lan
2005-09-21 17:12 ` Hugh Dickins
2005-09-21 17:31 ` Jay Lan
2005-09-21 17:45 ` Christoph Lameter
2005-09-21 17:46 ` Hugh Dickins
2005-09-21 18:05 ` Jay Lan
2005-09-21 18:26 ` Frank van Maarseveen
2005-09-21 19:19 ` Hugh Dickins
2005-09-21 19:28 ` Frank van Maarseveen
2005-09-21 19:38 ` Jay Lan
2005-09-21 19:47 ` Hugh Dickins
2005-09-21 19:48 ` Frank van Maarseveen
2005-09-21 19:52 ` Hugh Dickins
2005-09-21 19:48 ` Christoph Lameter
2005-09-21 20:06 ` Hugh Dickins
2005-09-21 20:13 ` Christoph Lameter
2005-09-27 20:43 ` Jay Lan
2005-09-27 21:47 ` Jay Lan
2005-09-27 21:50 ` Christoph Lameter
2005-09-27 22:43 ` Jay Lan
2005-09-28 13:18 ` Hugh Dickins
2005-09-28 17:31 ` Jay Lan
2005-10-03 19:53 ` Hugh Dickins
2005-10-04 8:59 ` Frank van Maarseveen
2005-10-04 21:48 ` Jay Lan
2005-10-07 2:09 ` Jay Lan
2005-10-07 3:03 ` Hugh Dickins [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=Pine.LNX.4.61.0510070354590.16857@goblin.wat.veritas.com \
--to=hugh@veritas.com \
--cc=clameter@engr.sgi.com \
--cc=daw@sgi.com \
--cc=frankvm@frankvm.com \
--cc=jlan@engr.sgi.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®