From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Jay Lan <jlan@sgi.com>, Oleg Nesterov <oleg@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jiri Pirko <jpirko@redhat.com>,
linux-kernel@vger.kernel.org, Jonathan Lim <jlim@sgi.com>
Subject: Re: [PATCH] introduce get_mm_hiwater_xxx(), fix taskstats->hiwater_xxx accounting
Date: Sat, 6 Dec 2008 16:09:04 +0530 [thread overview]
Message-ID: <20081206103904.GC24782@balbir.in.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0812060950120.22390@blonde.anvils>
* Hugh Dickins <hugh@veritas.com> [2008-12-06 09:56:19]:
> On Sat, 6 Dec 2008, Balbir Singh wrote:
> >
> > Yes, true and getdelays can display all the exported information.
> >
> > The race does seem concerning, I would vote for keeping the update in
> > there and disabling preemption around the update, so that hiwater
> > cannot swing back and forth.
>
> ?? Oleg is _fixing_ a race by removing the update from do_exit();
> and he is fixing the way the hiwater info was collected in tsacct.c.
I see that change and the reasoning seems accurate that we can query
the task at anytime, but I worry that if taskstats is not enabled, we'll
never call update_hiwater.* on the exiting task.
I wonder if a thread came in and like Oleg said, did (without taskstats
enabled)
free(malloc(some size)), followed by exit()
whether task_mem() would show the correct results for hiwater.*. I
should try it out and look more closely at the code as well.
--
Balbir
next prev parent reply other threads:[~2008-12-06 10:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 18:12 Oleg Nesterov
2008-12-03 20:24 ` Hugh Dickins
2008-12-04 13:52 ` Oleg Nesterov
2008-12-05 12:54 ` Hugh Dickins
2008-12-05 18:41 ` Jay Lan
2008-12-06 8:42 ` Balbir Singh
2008-12-06 9:56 ` Hugh Dickins
2008-12-06 10:39 ` Balbir Singh [this message]
2008-12-07 16:17 ` Oleg Nesterov
2008-12-07 16:58 ` Balbir Singh
2008-12-07 17:28 ` Oleg Nesterov
2008-12-07 17:39 ` Balbir Singh
2008-12-06 15:26 ` 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=20081206103904.GC24782@balbir.in.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=hugh@veritas.com \
--cc=jlan@sgi.com \
--cc=jlim@sgi.com \
--cc=jpirko@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®