All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Hugh Dickins <hugh@veritas.com>
Cc: kosaki.motohiro@jp.fujitsu.com, jpirko@redhat.com,
	linux-kernel@vger.kernel.org, oleg@redhat.com,
	linux-mm@kvack.org, mingo@elte.hu
Subject: Re: [PATCH for -mm] getrusage: fill ru_maxrss value
Date: Wed, 17 Jun 2009 13:21:18 -0700	[thread overview]
Message-ID: <20090617132118.ef839ad7.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0904060811300.22841@blonde.anvils>

On Mon, 6 Apr 2009 08:22:07 +0100 (BST)
Hugh Dickins <hugh@veritas.com> wrote:

> On Mon, 6 Apr 2009, KOSAKI Motohiro wrote:
> > 
> > > 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 :)
> 
> Ah, thank you.
> 
> > 
> > Do I must change test program?
> 
> Apparently somebody needs to, please; though it appears to be already
> well supplied with usleep(1)s - maybe they needed to be usleep(2)s?
> 
> And then change results shown in the changelog, and check conclusions
> drawn from them (if BSD is behaving as we do, it should still show
> maxrss not inherited over fork, but less obviously - the number goes
> down slightly, because the history is lost, but nowhere near to zero).
> 

afaik none of this happened, so I have the patch on hold.

WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Hugh Dickins <hugh@veritas.com>
Cc: kosaki.motohiro@jp.fujitsu.com, jpirko@redhat.com,
	linux-kernel@vger.kernel.org, oleg@redhat.com,
	linux-mm@kvack.org, mingo@elte.hu
Subject: Re: [PATCH for -mm] getrusage: fill ru_maxrss value
Date: Wed, 17 Jun 2009 13:21:18 -0700	[thread overview]
Message-ID: <20090617132118.ef839ad7.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0904060811300.22841@blonde.anvils>

On Mon, 6 Apr 2009 08:22:07 +0100 (BST)
Hugh Dickins <hugh@veritas.com> wrote:

> On Mon, 6 Apr 2009, KOSAKI Motohiro wrote:
> > 
> > > 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 :)
> 
> Ah, thank you.
> 
> > 
> > Do I must change test program?
> 
> Apparently somebody needs to, please; though it appears to be already
> well supplied with usleep(1)s - maybe they needed to be usleep(2)s?
> 
> And then change results shown in the changelog, and check conclusions
> drawn from them (if BSD is behaving as we do, it should still show
> maxrss not inherited over fork, but less obviously - the number goes
> down slightly, because the history is lost, but nowhere near to zero).
> 

afaik none of this happened, so I have the patch on hold.

--
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-06-17 20:22 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-30 11:15 [PATCH for -mm] getrusage: fill ru_maxrss value KOSAKI Motohiro
2008-12-30 11:15 ` KOSAKI Motohiro
2008-12-31 10:08 ` Jiri Pirko
2008-12-31 10:08   ` Jiri Pirko
2008-12-31 12:42   ` KOSAKI Motohiro
2008-12-31 12:42     ` KOSAKI Motohiro
2008-12-31 18:08     ` Jiri Pirko
2008-12-31 18:08       ` Jiri Pirko
2009-01-03 17:59     ` Oleg Nesterov
2009-01-03 17:59       ` Oleg Nesterov
2009-01-03 21:13       ` KOSAKI Motohiro
2009-01-03 21:13         ` KOSAKI Motohiro
2009-01-05 15:32         ` Jiri Pirko
2009-01-05 15:32           ` Jiri Pirko
2009-01-05 22:13           ` Andrew Morton
2009-01-05 22:13             ` Andrew Morton
2009-01-06  9:48             ` Jiri Pirko
2009-01-06  9:48               ` Jiri Pirko
2009-04-02 20:47               ` Andrew Morton
2009-04-02 20:47                 ` Andrew Morton
2009-04-02 21:13                 ` Ingo Molnar
2009-04-02 21:13                   ` Ingo Molnar
2009-04-05  8:49                   ` Jiri Pirko
2009-04-05  8:49                     ` Jiri Pirko
2009-04-05 17:24                     ` Hugh Dickins
2009-04-05 17:24                       ` Hugh Dickins
2009-04-06  0:21                       ` KOSAKI Motohiro
2009-04-06  0:21                         ` KOSAKI Motohiro
2009-04-06  7:22                         ` Hugh Dickins
2009-04-06  7:22                           ` Hugh Dickins
2009-06-17 20:21                           ` Andrew Morton [this message]
2009-06-17 20:21                             ` Andrew Morton
2009-06-18  0:57                             ` KOSAKI Motohiro
2009-06-18  0:57                               ` KOSAKI Motohiro
2009-09-07  2:58                               ` KOSAKI Motohiro
2009-09-07  2:58                                 ` KOSAKI Motohiro
2009-09-09 20:46                                 ` Andrew Morton
2009-09-09 20:46                                   ` Andrew Morton
2009-09-09 23:17                                   ` KOSAKI Motohiro
2009-09-09 23:17                                     ` KOSAKI Motohiro
2009-09-09 23:32                                     ` Andrew Morton
2009-09-09 23:32                                       ` Andrew Morton
2009-09-09 23:37                                       ` KOSAKI Motohiro
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=20090617132118.ef839ad7.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=hugh@veritas.com \
    --cc=jpirko@redhat.com \
    --cc=kosaki.motohiro@jp.fujitsu.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 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.