From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Mike D. Day" Subject: Re: FW: Is it a correct place for VBD information? Date: Fri, 23 Jun 2006 12:12:05 -0400 Message-ID: <449C12D5.9000800@us.ibm.com> References: <057001c696b9$7d66e7d0$4c87380a@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: <057001c696b9$7d66e7d0$4c87380a@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: > 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