From: Anthony Liguori <aliguori@us.ibm.com>
To: Satoshi Uchida <s-uchida@ap.jp.nec.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH 1/3] Output Virtual Block Device requests information to /proc/xen/vbd
Date: Wed, 21 Jun 2006 06:47:25 -0500 [thread overview]
Message-ID: <449931CD.1050806@us.ibm.com> (raw)
In-Reply-To: <004501c69523$bbd0b8d0$2c87380a@ad.spf.cl.nec.co.jp>
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
>
next prev parent reply other threads:[~2006-06-21 11:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 11:13 Re:[PATCH 1/3] Output Virtual Block Device requests information to /proc/xen/vbd Satoshi Uchida
2006-06-21 11:47 ` Anthony Liguori [this message]
2006-06-21 12:30 ` [PATCH " Keir Fraser
2006-06-21 14:33 ` Anthony Liguori
-- strict thread matches above, loose matches on Subject: below --
2006-06-22 9:17 Satoshi Uchida
2006-06-22 0:54 Satoshi Uchida
2006-06-22 6:48 ` Keir Fraser
2006-06-21 9:51 Satoshi Uchida
2006-06-21 10:05 ` NAHieu
2006-06-21 10:25 ` Satoshi Uchida
2006-06-21 10:36 ` Keir Fraser
2006-06-21 16:13 ` NAHieu
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=449931CD.1050806@us.ibm.com \
--to=aliguori@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.