From: Patrick Ohly <patrick.ohly@intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/4] system statistics sampling
Date: Mon, 28 Nov 2016 16:15:05 +0100 [thread overview]
Message-ID: <cover.1480345719.git.patrick.ohly@intel.com> (raw)
These patches are a precondition for the corresponding patches to
OE-core. See https://bugzilla.yoctoproject.org/show_bug.cgi?id=10583
The original motivation for the heartbeat event was the system
statistics sampling, but it also turned out to be useful for
monitoring disks more deterministically. That improvement is also
included here and shows that the heartbeat mechanism is useful also
without the OE-core patches.
The following changes since commit d140f0ee6f301264e226914766d9f63558acfd6c:
COW.py: fix sample codes (2016-11-23 10:59:49 +0000)
are available in the git repository at:
git://github.com/pohly/bitbake heartbeat
https://github.com/pohly/bitbake/tree/heartbeat
Patrick Ohly (4):
cooker process: fire heartbeat event at regular time intervals
runqueue.py: monitor disk space at regular time intervals
monitordisk.py: minor code and comment cleanup
monitordisk: add event
lib/bb/event.py | 27 +++++++++++++++++++++++++++
lib/bb/monitordisk.py | 23 ++++++++++++++---------
lib/bb/runqueue.py | 8 +++++---
lib/bb/server/process.py | 25 +++++++++++++++++++++++++
lib/bb/ui/knotty.py | 1 +
lib/bb/ui/toasterui.py | 3 +++
6 files changed, 75 insertions(+), 12 deletions(-)
--
2.1.4
next reply other threads:[~2016-11-28 15:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 15:15 Patrick Ohly [this message]
2016-11-28 15:15 ` [PATCH 1/4] cooker process: fire heartbeat event at regular time intervals Patrick Ohly
2016-11-28 15:15 ` [PATCH 2/4] runqueue.py: monitor disk space " Patrick Ohly
2016-11-28 15:58 ` Richard Purdie
2016-11-28 16:30 ` Patrick Ohly
2016-11-28 15:15 ` [PATCH 3/4] monitordisk.py: minor code and comment cleanup Patrick Ohly
2016-11-28 15:15 ` [PATCH 4/4] monitordisk: add event Patrick Ohly
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=cover.1480345719.git.patrick.ohly@intel.com \
--to=patrick.ohly@intel.com \
--cc=bitbake-devel@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.