From: "Mike D. Day" <ncmike@us.ibm.com>
To: Satoshi Uchida <s-uchida@ap.jp.nec.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: FW: Is it a correct place for VBD information?
Date: Fri, 23 Jun 2006 12:12:05 -0400 [thread overview]
Message-ID: <449C12D5.9000800@us.ibm.com> (raw)
In-Reply-To: <057001c696b9$7d66e7d0$4c87380a@ad.spf.cl.nec.co.jp>
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
next prev parent reply other threads:[~2006-06-23 16:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 11:38 FW: Is it a correct place for VBD information? Satoshi Uchida
2006-06-23 16:12 ` Mike D. Day [this message]
2006-06-26 2:03 ` Satoshi Uchida
2006-06-26 21:09 ` Keir Fraser
2006-06-27 5:45 ` Satoshi Uchida
2006-06-27 10:01 ` Keir Fraser
[not found] <2e4c8dd38360b9ba7993cc9de7dba768@cl.cam.ac.uk>
2006-06-28 1:15 ` Satoshi Uchida
2006-06-28 6:46 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=449C12D5.9000800@us.ibm.com \
--to=ncmike@us.ibm.com \
--cc=s-uchida@ap.jp.nec.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.