All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] [Yocto Bug 1700] Fix for buildstats diskio on	non physical disks
Date: Tue, 08 Nov 2011 14:12:38 +0000	[thread overview]
Message-ID: <1320761558.10843.39.camel@ted> (raw)
In-Reply-To: <4EB90155.3070705@hale.at>

On Tue, 2011-11-08 at 11:15 +0100, Wolfram Stering wrote:
> On 11/02/2011 07:41 AM, Beth Flanagan wrote:
> > From: Elizabeth Flanagan <elizabeth.flanagan@intel.com>
> >
> > tmpfs/encryptfs/ramfs have no entry in /proc/diskstats. This modifies 
> > buildstats to not collect diskio statistics when we encounter a case where 
> > the os.major/os.minor is not represented with an entry in /proc/diskstats.
> 
> A similar issue exists for building on a btrfs partition.
> I posted a message on Oct 28 concerning buildstats on btrfs volumes.
> The problem there is, that btrfs's stat() reports fake device ids that
> cannot be found in /proc/diskstats.

Did this patch help address that problem for you too?

Cheers,

Richard




  reply	other threads:[~2011-11-08 14:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-02  6:41 [PATCH 0/1] [Yocto Bug 1700] Fix for buildstats diskio on non physical disks Beth Flanagan
2011-11-02  6:41 ` [PATCH 1/1] [Yocto Bug 1700] Fix for buildstats on tmpfs Beth Flanagan
2011-11-07 17:50   ` Saul Wold
2011-11-08 10:15 ` [PATCH 0/1] [Yocto Bug 1700] Fix for buildstats diskio on non physical disks Wolfram Stering
2011-11-08 14:12   ` Richard Purdie [this message]
2011-11-08 15:53     ` Wolfram Stering
2011-11-08 15:57       ` Flanagan, Elizabeth
2011-11-09 12:00         ` Wolfram Stering
2011-11-09 18:11           ` Flanagan, Elizabeth
2011-11-09 12:13         ` Koen Kooi
2011-11-09 18:21           ` Flanagan, Elizabeth

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=1320761558.10843.39.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    /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.