From: Jesse Barnes <jbarnes@sgi.com>
To: Guillaume Thouvenin <guillaume.thouvenin@bull.net>
Cc: Jay Lan <jlan@sgi.com>, Andrew Morton <akpm@osdl.org>,
lkml <linux-kernel@vger.kernel.org>,
Tim Schmielau <tim@physik3.uni-rostock.de>,
Kaigai Kohei <kaigai@ak.jp.nec.com>
Subject: Re: [PATCH 2.6.11-rc4-mm1] end-of-proces handling for acct-csa
Date: Wed, 2 Mar 2005 09:56:57 -0800 [thread overview]
Message-ID: <200503020956.57637.jbarnes@sgi.com> (raw)
In-Reply-To: <1109749735.8422.104.camel@frecb000711.frec.bull.fr>
On Tuesday, March 1, 2005 11:48 pm, Guillaume Thouvenin wrote:
> Is it possible to merge BSD and CSA? I mean with CSA, there is a part
> that does per-process accounting. For exemple in the
> linux-2.6.9.acct_mm.patch the two functions update_mem_hiwater() and
> csa_update_integrals() update fields in the current (and parent)
> process. So maybe you can improve the BSD per-process accounting or
> maybe CSA can replace the BSD per-process accounting?
The BSD accounting tools will expect the data to be written in a certain
format, so we can't change that. We could, however, unify the data
collection under CONFIG_ACCOUNTING or something, that collects all the data
available (which would be the sum of the data collected by the BSD and CSA
calls) and then throw away data when writing to the BSD log so its format
remains the same.
That would simplify data collection since there would just be one set of
calls, and data reporting could be driven by userspace (whether it's in
old-style sys_acct format, or new-style data that CSA/ELSA defines).
Jesse
next prev parent reply other threads:[~2005-03-02 17:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-25 4:26 [PATCH 2.6.11-rc4-mm1] end-of-proces handling for acct-csa Jay Lan
2005-02-25 4:46 ` Andrew Morton
2005-02-25 6:57 ` Guillaume Thouvenin
2005-02-28 18:56 ` Jay Lan
2005-03-01 7:33 ` Guillaume Thouvenin
2005-03-01 18:06 ` Jay Lan
2005-03-02 7:48 ` Guillaume Thouvenin
2005-03-02 17:56 ` Jesse Barnes [this message]
2005-03-02 17:59 ` Jay Lan
2005-03-05 6:29 ` Tim Schmielau
2005-03-07 23:57 ` Jay Lan
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=200503020956.57637.jbarnes@sgi.com \
--to=jbarnes@sgi.com \
--cc=akpm@osdl.org \
--cc=guillaume.thouvenin@bull.net \
--cc=jlan@sgi.com \
--cc=kaigai@ak.jp.nec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tim@physik3.uni-rostock.de \
/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