From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Jay Lan <jlan@engr.sgi.com>
Cc: Andrew Morton <akpm@osdl.org>,
Guillaume Thouvenin <guillaume.thouvenin@bull.net>,
greg@kroah.com, linux-kernel@vger.kernel.org,
efocht@hpce.nec.com, linuxram@us.ibm.com, gh@us.ibm.com,
elsa-devel@lists.sourceforge.net, aquynh@gmail.com,
dean-list-linux-kernel@arctic.org, pj@sgi.com
Subject: Re: [patch 2.6.12-rc1-mm4] fork_connector: add a fork connector
Date: Fri, 01 Apr 2005 11:52:48 +0400 [thread overview]
Message-ID: <1112341968.9334.109.camel@uganda> (raw)
In-Reply-To: <424C9177.1070404@engr.sgi.com>
[-- Attachment #1: Type: text/plain, Size: 1524 bytes --]
On Thu, 2005-03-31 at 16:10 -0800, Jay Lan wrote:
> Andrew Morton wrote:
>
> >Guillaume Thouvenin <guillaume.thouvenin@bull.net> wrote:
> >
> >
> >> This patch adds a fork connector in the do_fork() routine.
> >>...
> >>
> >> The fork connector is used by the Enhanced Linux System Accounting
> >>project http://elsa.sourceforge.net
> >>
> >>
> >
> >Does it also meet all the in-kernel requirements for other accounting
> >projects?
> >
> >If not, what else do those other projects need?
> >
> >
> Hi Andrew,
>
> As the discussion in this thread of the past few days showed, this
> patch intends to take care of process grouping, but not the
> accounting data collection. Besides my concern of possibility of
> data loss, this patch also provides CSA information to handle process
> grouping as it intends to do. I plan to run some testing to see percentage
> of data loss when system is under stress test, but improvement at
> CBUS as Evgeniy indicated should help!
>
> Please be advised that i still need an do_exit handling to save accounting
> data. But, it is a separate issue.
My five copecks [or two cents]:
fork connector with CBUS [with theirs upto 2.5 % degradation
with huge disk writes per fork] are still much faster than any existing
accounting models.
But it is purely accounting project author to think about
accounting design though...
> Thanks,
> - jay
--
Evgeniy Polyakov
Crash is better than data corruption -- Arthur Grabowski
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-04-01 7:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-31 13:59 [patch 2.6.12-rc1-mm4] fork_connector: add a fork connector Guillaume Thouvenin
2005-03-31 22:44 ` Andrew Morton
2005-04-01 0:10 ` Jay Lan
2005-04-01 7:52 ` Evgeniy Polyakov [this message]
2005-04-07 22:40 ` Jay Lan
2005-04-07 22:47 ` Jay Lan
2005-04-08 10:24 ` Evgeniy Polyakov
2005-04-08 10:52 ` Evgeniy Polyakov
2005-04-08 20:27 ` Jay Lan
2005-04-08 22:08 ` Jay Lan
2005-04-08 22:18 ` Evgeniy Polyakov
2005-04-09 3:31 ` Jay Lan
2005-04-09 6:29 ` Evgeniy Polyakov
2005-04-11 5:43 ` Jay Lan
2005-04-11 6:44 ` Evgeniy Polyakov
2005-04-11 6:51 ` Andrew Morton
2005-04-11 7:31 ` Evgeniy Polyakov
2005-03-31 22:53 ` Andrew Morton
2005-04-01 10:56 ` Guillaume Thouvenin
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=1112341968.9334.109.camel@uganda \
--to=johnpol@2ka.mipt.ru \
--cc=akpm@osdl.org \
--cc=aquynh@gmail.com \
--cc=dean-list-linux-kernel@arctic.org \
--cc=efocht@hpce.nec.com \
--cc=elsa-devel@lists.sourceforge.net \
--cc=gh@us.ibm.com \
--cc=greg@kroah.com \
--cc=guillaume.thouvenin@bull.net \
--cc=jlan@engr.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=pj@sgi.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