From: Peter Zijlstra <peterz@infradead.org>
To: Martin Steigerwald <martin@lichtvoll.de>
Cc: Martin Steigerwald <martin.steigerwald@teamix.de>,
Ingo Molnar <mingo@kernel.org>, Andrew Morton <akpm@osdl.org>,
Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
Nicolas Dichtel <nicolas.dichtel@6wind.com>,
Jay Lan <jlan@engr.sgi.com>,
Gerlof Langeveld <gerlof.langeveld@atoptool.nl>,
Marc Haber <mh+debian-packages@zugschlus.de>,
bsingharora@gmail.com
Subject: Re: [REGRESSION] Two issues that prevent process accounting (taskstats) from working correctly
Date: Mon, 19 Dec 2016 15:02:02 +0100 [thread overview]
Message-ID: <20161219140202.GI3107@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1657770.QZ4bSFPITW@merkaba>
On Mon, Dec 19, 2016 at 02:50:25PM +0100, Martin Steigerwald wrote:
> Am Montag, 19. Dezember 2016, 14:19:11 CET schrieb Peter Zijlstra:
> > On Mon, Dec 19, 2016 at 01:06:00PM +0100, Martin Steigerwald wrote:
> > > Hello Ingo, Peter, Nicolas, Andrew, Balbir, Shailabh, Jay, Gerlof and
> > > Marc,
> > >
> > > starting from a Debian bug report of mine, Gerlof Langeveld, developer of
> > > system and process monitor atop¹, found two issues with process
> > > accounting.
> >
> > While $subject says regression the rest of the email completely fails to
> > mentions if this ever worked, and if so, against what version.
>
> Sorry for not mentioning it here. With kernel 3.16 process accounting worked
> nicely. We do not have any data on the exact kernel version where it started
> to fail. I do see these issues since quite a while, but I was never sure
> whether it was an issue in atop or the kernel and I do not recall on what
> exact combination of atop + kernel version it failed to work.
>
> As an additional notice: The mail addresses of Balbir and Shailabh which I got
> from source code annotations of taskstats.c and getdelays.c do not work
> anymore.
Right, Balbir is back with IBM and working on Linux again, but under a
different email address (and on a different continent). I've amended
his address and bounced him the initial email.
next prev parent reply other threads:[~2016-12-19 14:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 12:06 [REGRESSION] Two issues that prevent process accounting (taskstats) from working correctly Martin Steigerwald
2016-12-19 13:19 ` Peter Zijlstra
2016-12-19 13:50 ` Martin Steigerwald
2016-12-19 14:02 ` Peter Zijlstra [this message]
2016-12-19 17:25 ` Peter Zijlstra
2017-02-06 10:39 ` Martin Steigerwald
2017-02-06 16:20 ` Tejun Heo
2017-02-06 18:24 ` [PATCH] cpumask: use nr_cpumask_bits for parsing functions Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2017-02-10 21:56 [REGRESSION] Two issues that prevent process accounting (taskstats) from working correctly Dmitry Romanov
2017-02-12 15:44 ` Dmitry Romanov
2017-03-08 11:14 ` Richard Genoud
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=20161219140202.GI3107@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@osdl.org \
--cc=bsingharora@gmail.com \
--cc=gerlof.langeveld@atoptool.nl \
--cc=jlan@engr.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.steigerwald@teamix.de \
--cc=martin@lichtvoll.de \
--cc=mh+debian-packages@zugschlus.de \
--cc=mingo@elte.hu \
--cc=mingo@kernel.org \
--cc=nicolas.dichtel@6wind.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