linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: kosaki.motohiro@jp.fujitsu.com, Jiri Pirko <jpirko@redhat.com>,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	oleg@redhat.com, linux-mm@kvack.org, mingo@elte.hu
Subject: Re: [PATCH for -mm] getrusage: fill ru_maxrss value
Date: Mon,  6 Apr 2009 09:21:34 +0900 (JST)	[thread overview]
Message-ID: <20090406091825.44F0.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0904051736210.23536@blonde.anvils>

Hi

> I'm worrying particularly about the fork/exec issue you highlight.
> You're exemplary in providing your test programs, but there's a big
> omission: you don't mention that the first test, "./getrusage -lc",
> gives a very different result on Linux than you say it does on BSD -
> you say the BSD fork line is "fork: self 0 children 0", whereas
> I find my Linux fork line is "fork: self 102636 children 0".

FreeBSD update rusage at tick updating point. (I think all bsd do that)
Then, bsd displaing 0 is bsd's problem :)

Do I must change test program?

> So after that discrepancy, I can't tell what to expect.  Not that
> I can make any sense of BSD's "self 0" there - I don't know how
> you could present 0 there if this is related to hiwater_rss.
> 
> Now I'm seriously wondering if the ru_maxrss reported will generate
> more bugreports from people puzzled as to how it should behave,
> than help anyone in studying their process behaviour.
> 
> Sorry to be so negative after all this time: I genuinely hope others
> will spring up to defend your patch and illustrate my stupidity.





--
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>

  reply	other threads:[~2009-04-06  0:21 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-30 11:15 KOSAKI Motohiro
2008-12-31 10:08 ` Jiri Pirko
2008-12-31 12:42   ` KOSAKI Motohiro
2008-12-31 18:08     ` Jiri Pirko
2009-01-03 17:59     ` Oleg Nesterov
2009-01-03 21:13       ` KOSAKI Motohiro
2009-01-05 15:32         ` Jiri Pirko
2009-01-05 22:13           ` Andrew Morton
2009-01-06  9:48             ` Jiri Pirko
2009-04-02 20:47               ` Andrew Morton
2009-04-02 21:13                 ` Ingo Molnar
2009-04-05  8:49                   ` Jiri Pirko
2009-04-05 17:24                     ` Hugh Dickins
2009-04-06  0:21                       ` KOSAKI Motohiro [this message]
2009-04-06  7:22                         ` Hugh Dickins
2009-06-17 20:21                           ` Andrew Morton
2009-06-18  0:57                             ` KOSAKI Motohiro
2009-09-07  2:58                               ` KOSAKI Motohiro
2009-09-09 20:46                                 ` Andrew Morton
2009-09-09 23:17                                   ` KOSAKI Motohiro
2009-09-09 23:32                                     ` Andrew Morton
2009-09-09 23:37                                       ` KOSAKI Motohiro

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=20090406091825.44F0.A69D9226@jp.fujitsu.com \
    --to=kosaki.motohiro@jp.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=hugh@veritas.com \
    --cc=jpirko@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@elte.hu \
    --cc=oleg@redhat.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