From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [PATCH 1/3] Output Virtual Block Device requests information to /proc/xen/vbd Date: Wed, 21 Jun 2006 06:47:25 -0500 Message-ID: <449931CD.1050806@us.ibm.com> References: <004501c69523$bbd0b8d0$2c87380a@ad.spf.cl.nec.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <004501c69523$bbd0b8d0$2c87380a@ad.spf.cl.nec.co.jp> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Satoshi Uchida Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Satoshi Uchida wrote: > Uom. > > In my subjective, currently, procfs is used for representing dynamic > information such as statistical data, and sysfs is used for representing > statical information such as module parameters. > /proc is for process information. This stuff definitely belongs in sysfs. It's analogous to /sys/class/net/eth0/statistics/. > In this case, I think that this I/O information is former, so information > is put into procfs in this time. > As similar example, ballon infromation exist in procfs. > The balloon driver shouldn't be using proc. Regards, Anthony Liguori > Is it better that realizing at sysfs? > > Thanks, > Satoshi UCHIDA > > ------------------------------------------------------------------------ > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >