From: Erich Focht <efocht@hpce.nec.com>
To: Guillaume Thouvenin <guillaume.thouvenin@bull.net>
Cc: Paul Jackson <pj@sgi.com>, Andrew Morton <akpm@osdl.org>,
Greg KH <greg@kroah.com>, lkml <linux-kernel@vger.kernel.org>,
elsa-devel <elsa-devel@lists.sourceforge.net>,
Gerrit Huizenga <gh@us.ibm.com>, Jay Lan <jlan@engr.sgi.com>
Subject: Re: [PATCH 2.6.11-rc3-mm2] connector: Add a fork connector
Date: Mon, 21 Feb 2005 17:55:00 +0100 [thread overview]
Message-ID: <200502211755.00795.efocht@hpce.nec.com> (raw)
In-Reply-To: <1108997033.8418.193.camel@frecb000711.frec.bull.fr>
On Monday 21 February 2005 15:43, Guillaume Thouvenin wrote:
>
> I also choose this implementation because Erich Focht wrote in the
> email http://lkml.org/lkml/2004/12/17/99 that keeps the historic about
> the creation of processes "sounds very useful for a lot of interesting
> stuff". So I thought about something that can be used by other
> application and with netlink, information is available to everyone.
Besides accounting I had in mind something like cluster-wide pid
tracking in userspace with builtin relationship information. A bit of
single system image integration... As I don't have it, yet, I'm not
(yet) a very strong requester for the service provided by your
module. But I still think it's usefull and might want later a hook on
exit, too. (And yes, I can imagine of other ways to get the data
effectively out of the kernel, too).
> Results are:
>
> kernel without fork connector
> real : 8m17.042s 8m10.113s 8m08.597s 8m10.068s 8m08.930s
> user : 7m32.376s 7m35.985s 7m34.424s 7m34.221s 7m34.835s
> sys : 0m50.730s 0m51.139s 0m51.159s 0m51.406s 0m51.020s
>
> kernel with the fork connector
> real : 8m14.492s 8m08.656s 8m07.754s 8m08.002s 8m07.854s
> user : 7m31.664s 7m33.528s 7m33.625s 7m33.500s 7m33.822s
> sys : 0m50.651s 0m51.222s 0m51.102s 0m51.367s 0m50.894s
>
> kernel with the fork connector + application listens
> real : 8m08.596s 8m08.950s 8m08.899s 8m08.678s 8m08.987s
> user : 7m33.312s 7m33.898s 7m34.004s 7m33.285s 7m33.628s
> sys : 0m52.222s 0m52.013s 0m51.809s 0m52.361s 0m52.036s
I liked the previous lean implementation more, but the performance
of this one doesn't look at all as scary as I thought.
Best regards,
Erich
next prev parent reply other threads:[~2005-02-21 16:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-17 14:55 [PATCH 2.6.11-rc3-mm2] connector: Add a fork connector Guillaume Thouvenin
2005-02-17 15:50 ` Evgeniy Polyakov
2005-02-21 7:07 ` Guillaume Thouvenin
2005-02-21 8:41 ` Evgeniy Polyakov
2005-02-21 9:47 ` Paul Jackson
2005-02-21 10:33 ` Guillaume Thouvenin
2005-02-21 11:58 ` Paul Jackson
2005-02-21 14:43 ` Guillaume Thouvenin
2005-02-21 16:55 ` Erich Focht [this message]
2005-02-21 17:54 ` Paul Jackson
2005-02-21 8:05 ` [Elsa-devel] " Guillaume Thouvenin
2005-02-21 8:48 ` Evgeniy Polyakov
[not found] <1108649153.8379.137.camel@frecb000711.frec.bull.fr>
2005-02-23 8:52 ` Guillaume Thouvenin
2005-02-23 9:07 ` Andrew Morton
2005-02-23 11:08 ` Evgeniy Polyakov
2005-02-23 10:58 ` Andrew Morton
2005-02-23 11:41 ` Evgeniy Polyakov
2005-02-24 6:41 ` Guillaume Thouvenin
2005-02-24 9:17 ` Evgeniy Polyakov
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=200502211755.00795.efocht@hpce.nec.com \
--to=efocht@hpce.nec.com \
--cc=akpm@osdl.org \
--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=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