Date: Mon, 7 Aug 2006 02:30:25 -0700
From: Paul Jackson <pj@sgi.com>
To: Kirill Korotaev <dev@sw.ru>
Cc: nagar@watson.ibm.com, akpm@osdl.org, vatsa@in.ibm.com, mingo@elte.hu,
       nickpiggin@yahoo.com.au, sam@vilain.net, linux-kernel@vger.kernel.org,
       dev@openvz.org, efault@gmx.de, balbir@in.ibm.com, sekharan@us.ibm.com,
       haveblue@us.ibm.com
Subject: Re: [ProbableSpam] Re: [RFC, PATCH 0/5] Going forward with Resource
 Management - A cpu  controller
Message-Id: <20060807023025.2c44f3d1.pj@sgi.com>
In-Reply-To: <44D6EBEF.9010804@sw.ru>
References: <20060804050753.GD27194@in.ibm.com>
	<20060803223650.423f2e6a.akpm@osdl.org>
	<44D35794.2040003@sw.ru>
	<44D367F3.8060108@watson.ibm.com>
	<44D6EBEF.9010804@sw.ru>
Organization: SGI
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1105
Lines: 25

Kirill wrote:
> > A filesystem based interface is useful when you have hierarchies (as resource
> > groups and cpusets do) since it naturally defines a convenient to use
> > hierarchical namespace.
> but it is not much convinient for applications then.

Is this simply a language issue?  File systems hierarchies
are more easily manipulated with shell utilities (ls, cat,
find, grep, ...) and system call API's are easier to access
from C?

If so, then perhaps all that's lacking for convenient C access
to a filesystem based interface is a good library, that presents
an API convenient for use from C code, but underneath makes the
necessary file system calls (open, read, diropen, stat, ...).

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/