From: Limin Gu <limin@dbear.engr.sgi.com>
To: akpm@osdl.org (Andrew Morton)
Cc: linux-kernel@vger.kernel.org, lse-tech@lists.sourceforge.net,
limin@dbear.engr.sgi.com (Limin Gu)
Subject: Re: [patch] Job - inescapable job containers
Date: Thu, 20 Jan 2005 17:24:30 -0800 (PST) [thread overview]
Message-ID: <200501210124.j0L1OUE22333@dbear.engr.sgi.com> (raw)
In-Reply-To: <20050119170628.2429c41e.akpm@osdl.org> from "Andrew Morton" at Jan 19, 2005 05:06:28 PM
> I'm totally not in a position to evaluate the completeness, desirability,
> interest-level, etc of this patch, I'm afraid. This is an opportunity for
> other stakeholders to weigh in..
Thanks Andrew!
First, Job can work as a standalone kernel module.
The current implementation provides the inescapable job container.
Job provides global unique Job ID (jid) to processes in a cluster
environment. Job initiation on Linux is performed via a PAM session
module with authentication and security checks. Root level processes,
or those with the CAP_SYS_RESOURCE capability, can create new jobs
or escape from a job.
Second, Job based batch schedulers or resource limit tools can take the
advantage of the process control ability Job provides.
Thrid, Job provides a registion mechanism to various accounting modules
for setting and getting job based accounting information.
CSA (Comprehensive System Accounting) is one example of the accounting
modules, (CSA code maintainer Jay Lan is currently on vacation, he will
be back at Feb. 1).
We are pushing Job to linux kernel. If anybody has been using Job in your
open source software, please respond to show the desirability and
interest-level for Job, and we highly appreciate your suggestion on its
completeness as well.
Thank you!
--Limin
next prev parent reply other threads:[~2005-01-21 1:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 23:43 Limin Gu
2005-01-20 1:06 ` Andrew Morton
2005-01-21 1:24 ` Limin Gu [this message]
2005-01-20 9:28 Guillaume Thouvenin
2005-01-20 12:42 ` 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=200501210124.j0L1OUE22333@dbear.engr.sgi.com \
--to=limin@dbear.engr.sgi.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®