All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: 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 09:33:45 -0500	[thread overview]
Message-ID: <pan.2006.06.21.14.33.45.164078@us.ibm.com> (raw)
In-Reply-To: 7b0e62909852d221b9c21f3519228feb@cl.cam.ac.uk

On Wed, 21 Jun 2006 13:30:34 +0100, Keir Fraser wrote:

> 
> 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.

Agreed!  It's a very common feature request so it'll be great to get this
in the tree.  This information is sort of available in
/sys/block/<backend-dev>/stat but it's not terribly reliable in my
experience (it's always zero's for loop devices IIRC).

These patches are missing Signed-Off-By lines too btw.  When you resubmit,
make sure to include those.

Thanks,

Anthony Liguori

>   -- Keir

  reply	other threads:[~2006-06-21 14:33 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 ` [PATCH " Anthony Liguori
2006-06-21 12:30   ` Keir Fraser
2006-06-21 14:33     ` Anthony Liguori [this message]
  -- 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=pan.2006.06.21.14.33.45.164078@us.ibm.com \
    --to=aliguori@us.ibm.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.