public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jay Lan <jlan@sgi.com>
To: Tim Schmielau <tim@physik3.uni-rostock.de>
Cc: Guillaume Thouvenin <guillaume.thouvenin@bull.net>,
	Andrew Morton <akpm@osdl.org>,
	lkml <linux-kernel@vger.kernel.org>,
	Kaigai Kohei <kaigai@ak.jp.nec.com>,
	jbarnes@sgi.com
Subject: Re: [PATCH 2.6.11-rc4-mm1] end-of-proces handling for acct-csa
Date: Mon, 07 Mar 2005 15:57:58 -0800	[thread overview]
Message-ID: <422CEA86.5090202@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0503050726090.31083@gockel.physik3.uni-rostock.de>

The patch i propose is tiny, simple and straight forward. It
touches only one file and leaves the CSA code in a  configurable
loadable module. It broke nobody's code and it does not need to
redesign existing BSD kernel code and utilities.

If we are to merge the code, there are some detailed discussion
needed to happen on implementation deail. We are talking about
supporting two different internal formats by one piece of code.
We need to maintain BSD acct format because BSD utilities count
on it.

If we are to combine two formats into one, we then need to
modify BSD utilies to understand the new format. How about
the backwards compatibility?

Now this is really an overkill. All i asked for was only
adding a few lines to acct.c.

Thanks,
  - jay


Tim Schmielau wrote:
> On Wed, 2 Mar 2005, 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?
> 
> 
> Yes, that was also my preferred direction - make CSA able to also write
> BSD acct format, and replace the existing BSD accounting with CSA.
> However it seems this will still increase the amount of kernel code quite 
> a bit.
> 
> Sorry for not going into any details, I have to leave right now and will 
> be offline for two weeks.
> 
> Tim


      reply	other threads:[~2005-03-08  0:06 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
2005-03-02 17:59             ` Jay Lan
2005-03-05  6:29             ` Tim Schmielau
2005-03-07 23:57               ` Jay Lan [this message]

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=422CEA86.5090202@sgi.com \
    --to=jlan@sgi.com \
    --cc=akpm@osdl.org \
    --cc=guillaume.thouvenin@bull.net \
    --cc=jbarnes@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