WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] FW: Is it a correct place for VBD information?

To: Satoshi Uchida <s-uchida@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] FW: Is it a correct place for VBD information?
From: "Mike D. Day" <ncmike@xxxxxxxxxx>
Date: Fri, 23 Jun 2006 12:12:05 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 23 Jun 2006 09:12:30 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <057001c696b9$7d66e7d0$4c87380a@xxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <057001c696b9$7d66e7d0$4c87380a@xxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.4 (Macintosh/20060530)
Satoshi Uchida wrote:
 A little while ago, I send modified VBD information patch.

However, I does not sit well with location.
I does not find statistical information under 'device' directory, and see them 
under 'class' directory for vif. (/sys/class/net) But, there are not 
appropriate location. (/sys/class/vbd or /sys/class/block)

Is it a correct place for such type of information?
Is it necessary to make symbolic links to other places?
Where is appropriate place?
Please comment.


I think that it is good to handle such information at one partial tree for 
management.
My idea is to take a kind of following structure for store such information.

   sys -- class -- xen --+-- domain0 --- balloon ( symlink to 
/sys/class/mem/balloon ?)
                                 |
+-- domain1 --+-- vbd --+-- vbd-x-xxxx(symlink?) | |
                                                     |            +-- total 
information file.
                                                     |
+-- vif -- vif-x-xxxx(symlink)


What about /sys/hypervisor/xen/domain/1/vbd

/sys/hypervisor is going into upstream linux, and that leaves /sys/hypervisor/xen/ as our namespace for info.

Mike

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel