[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH 1/3] Output Virtual Block Device requests information to /proc/xen/vbd

  • To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Satoshi Uchida" <s-uchida@xxxxxxxxxxxxx>
  • Date: Thu, 22 Jun 2006 09:54:44 +0900
  • Delivery-date: Wed, 21 Jun 2006 17:55:10 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcaVLnuF8lKTQO09Sl2/Ip3sYykZmAAYdmZwAAGDp0A=

Thanks, Feir and Anthony.

> On 21 Jun 2006, at 12:47, Anthony Liguori wrote:
>>> 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/.
>Yes. The patchset looks good and is obviously useful -- we'd like to apply it 
>if this gets fixed.
> -- Keir

It's OK.
I try to examine and develop transition to sysfs file system.

I may worry that where does information locate in sysfs.
In it case, I confer with you, so please give me nice answer.
Current, I think two pattern.
  1. vbd class create /sysfs/class.
  2. Use vbd-* directory under /sysfs/devices/xen-backend/.
May first idea be appropriate?

In addition,
The one of advantage for our method is to represent total information for 
This mechanism is useful for analysis for each domain I/O or total environments.
In sysfs, I see that Interface connect individual device/module information.
Naturally, it is enough by using xentop, but xentop can not take log file.
If xentop can be redirected to normal file, but it file insert binary code.
Aren't there any good ideas?

Satoshi UCHIDA

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.