All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: "Cooper Jr., Franklin" <fcooper@ti.com>
Cc: "meta-arago@arago-project.org" <meta-arago@arago-project.org>
Subject: Re: [PATCH 2/3] stress: Pull stress into meta-arago-extras
Date: Fri, 24 Jan 2014 14:23:43 -0500	[thread overview]
Message-ID: <20140124192343.GP30525@edge> (raw)
In-Reply-To: <8F29D6B095ED194EA1980491A5E029710C610AB5@DFLE08.ent.ti.com>

On Fri, Jan 24, 2014 at 10:20:26AM -0500, Cooper Jr., Franklin wrote:
> 
> 
> > -----Original Message-----
> > From: meta-arago-bounces@arago-project.org [mailto:meta-arago-
> > bounces@arago-project.org] On Behalf Of Cooper Jr., Franklin
> > Sent: Monday, January 20, 2014 9:32 PM
> > To: Dmytriyenko, Denys
> > Cc: meta-arago@arago-project.org
> > Subject: Re: [meta-arago] [PATCH 2/3] stress: Pull stress into meta-arago-extras
> > 
> > 
> > 
> > > On Jan 20, 2014, at 4:15 PM, "Dmytriyenko, Denys" <denys@ti.com> wrote:
> > >
> > >> On Mon, Jan 20, 2014 at 05:16:57PM -0600, Franklin S. Cooper Jr wrote:
> > >> * Stress is a useful userspace testing tool.
> > >> * The original recipe can be found in meta-linaro/meta-linaro/recipes-extra.
> > >> * However, to avoid pulling in that entire layer included bbappend
> > >> overrides  simply overlay the recipe into meta-arago-extras.
> > >
> > > Well, we are already cloning the entire repo anyway, even though only
> > > using meta-linaro-toolchain sub-layer. Are you afraid of any conflicts
> > > with their bbappends? I only see busybox being the obvious one, but we
> > > can BBMASK it for our distro... There are plenty of other useful
> > > testing tools, especially in master - are we interested?
> > > We've started talking to Linaro, so we may end up moving some of our
> > > recipes/enhancements back to their layer... Thoughts?
> > I'm ok with doing this.

> [Franklin] I thought about this more and would like to hold off adding this 
> layer as an meta-argao dependency for now. This would break things for 
> current users since it would require them to update their layer 
> configuration. I rather pull in stress as is now and add this new layer 
> dependency when we update meta-arago to support dora when we have to update 
> the configuration anyway. At that time we can also remove stress from 
> meta-arago as part of cleanup.

Sounds good. BTW, I was thinking to start making changes necessary for Dora in 
the master branch of meta-arago any time now. While there's now ti2013.12.x 
release maintenance branch, I may need to create a separate 'dylan' branch as 
well...


> > >> Signed-off-by: Franklin S. Cooper Jr <fcooper@ti.com>
> > >> ---
> > >> .../recipes-devtools/stress/files/texinfo.patch    |   79
> > ++++++++++++++++++++
> > >> .../recipes-devtools/stress/stress_1.0.4.bb        |   16 ++++
> > >> 2 files changed, 95 insertions(+), 0 deletions(-) create mode 100644
> > >> meta-arago-extras/recipes-devtools/stress/files/texinfo.patch
> > >> create mode 100644
> > >> meta-arago-extras/recipes-devtools/stress/stress_1.0.4.bb
> > >>
> > >> diff --git
> > >> a/meta-arago-extras/recipes-devtools/stress/files/texinfo.patch
> > >> b/meta-arago-extras/recipes-devtools/stress/files/texinfo.patch
> > >> new file mode 100644
> > >> index 0000000..5ac5951
> > >> --- /dev/null
> > >> +++ b/meta-arago-extras/recipes-devtools/stress/files/texinfo.patch
> > >> @@ -0,0 +1,79 @@
> > >> +--- a/doc/stress.texi
> > >> ++++ b/doc/stress.texi
> > >> +@@ -62,47 +62,47 @@
> > >> +
> > >> + @table @samp
> > >> + @item -?
> > >> +-@itemx --help
> > >> ++@item --help
> > >> + Show help information.
> > >> +
> > >> +-@itemx --version
> > >> ++@item --version
> > >> + Show version information.
> > >> +
> > >> + @item -v
> > >> +-@itemx --verbose
> > >> ++@item --verbose
> > >> + Turn up verbosity.
> > >> +
> > >> + @item -q
> > >> +-@itemx --quiet
> > >> ++@item --quiet
> > >> + Turn down verbosity.
> > >> +
> > >> + @item -n
> > >> +-@itemx --dry-run
> > >> ++@item --dry-run
> > >> + Show what would have been done.
> > >> +
> > >> + @item -t @var{secs}
> > >> +-@itemx --timeout @var{secs}
> > >> ++@item --timeout @var{secs}
> > >> + Time out after @var{secs} seconds.
> > >> +
> > >> +-@itemx --backoff @var{usecs}
> > >> ++@item --backoff @var{usecs}
> > >> + Wait for factor of @var{usecs} microseconds before starting work.
> > >> +
> > >> + @item -c @var{forks}
> > >> +-@itemx --cpu @var{forks}
> > >> ++@item --cpu @var{forks}
> > >> + Spawn @var{forks} processes each spinning on @samp{sqrt()}.
> > >> +
> > >> + @item -i @var{forks}
> > >> +-@itemx --io @var{forks}
> > >> ++@item --io @var{forks}
> > >> + Spawn @var{forks} processes each spinning on @samp{sync()}.
> > >> +
> > >> + @item -m @var{forks}
> > >> +-@itemx --vm @var{forks}
> > >> ++@item --vm @var{forks}
> > >> + Spawn @var{forks} processes each spinning on @samp{malloc()}.
> > >> +
> > >> +-@itemx --vm-bytes @var{bytes}
> > >> ++@item --vm-bytes @var{bytes}
> > >> + Allocate @var{bytes} number of bytes.  The default is 1.
> > >> +
> > >> +-@itemx --vm-hang
> > >> ++@item --vm-hang
> > >> + Instruct each vm hog process to go to sleep after allocating
> > >> +memory.  This  contrasts with their normal behavior, which is to
> > >> +free the memory and  reallocate @emph{ad infinitum}.  This is useful
> > >> +for simulating low memory @@ -114,13 +114,13 @@  @end example
> > >> +
> > >> + @item -d @var{forks}
> > >> +-@itemx --hdd @var{forks}
> > >> ++@item --hdd @var{forks}
> > >> + Spawn @var{forks} processes each spinning on @samp{write()}.
> > >> +
> > >> +-@itemx --hdd-bytes @var{bytes}
> > >> ++@item --hdd-bytes @var{bytes}
> > >> + Write @var{bytes} number of bytes.  The default is 1GB.
> > >> +
> > >> +-@itemx --hdd-noclean
> > >> ++@item --hdd-noclean
> > >> + Do not unlink file(s) to which random ASCII data is written.
> > >> +
> > >> + @end table
> > >> diff --git
> > >> a/meta-arago-extras/recipes-devtools/stress/stress_1.0.4.bb
> > >> b/meta-arago-extras/recipes-devtools/stress/stress_1.0.4.bb
> > >> new file mode 100644
> > >> index 0000000..04ad6ce
> > >> --- /dev/null
> > >> +++ b/meta-arago-extras/recipes-devtools/stress/stress_1.0.4.bb
> > >> @@ -0,0 +1,16 @@
> > >> +DESCRIPTION = "Deliberately simple workload generator for POSIX
> > >> +systems. It \ imposes a configurable amount of CPU, memory, I/O, and disk
> > stress on the system."
> > >> +HOMEPAGE = "http://people.seas.harvard.edu/~apw/stress/"
> > >> +LICENSE = "GPLv2"
> > >> +LIC_FILES_CHKSUM =
> > "file://COPYING;md5=d32239bcb673463ab874e80d47fae504"
> > >> +
> > >> +PR = "r0"
> > >> +
> > >> +SRC_URI = "http://pkgs.fedoraproject.org/repo/pkgs/stress/stress-
> > ${PV}.tar.gz/a607afa695a511765b40993a64c6e2f4/stress-${PV}.tar.gz \
> > >> +           file://texinfo.patch \
> > >> +           "
> > >> +
> > >> +SRC_URI[md5sum] = "a607afa695a511765b40993a64c6e2f4"
> > >> +SRC_URI[sha256sum] =
> > "369c997f65e8426ae8b318d4fdc8e6f07a311cfa77cc4b25dace465c582163c0
> > "
> > >> +
> > >> +inherit autotools
> > >> --
> > >> 1.7.0.4
> > >>
> > >> _______________________________________________
> > >> meta-arago mailing list
> > >> meta-arago@arago-project.org
> > >> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
> > _______________________________________________
> > meta-arago mailing list
> > meta-arago@arago-project.org
> > http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago


  reply	other threads:[~2014-01-24 19:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-20 23:16 [PATCH 1/3] ti-tisdk-setup: Update to support new u-boot, kernel and device Franklin S. Cooper Jr
2014-01-20 22:43 ` Denys Dmytriyenko
2014-01-20 23:16 ` [PATCH 2/3] stress: Pull stress into meta-arago-extras Franklin S. Cooper Jr
2014-01-20 22:15   ` Denys Dmytriyenko
2014-01-21  3:32     ` Cooper Jr., Franklin
2014-01-24 15:20       ` Cooper Jr., Franklin
2014-01-24 19:23         ` Denys Dmytriyenko [this message]
2014-01-20 23:16 ` [PATCH 3/3] packagegroup-arago-test: Add useful testing tools Franklin S. Cooper Jr
2014-01-20 22:45   ` Denys Dmytriyenko
2014-01-28 20:27     ` Denys Dmytriyenko
2014-01-28 21:51     ` Cooper Jr., Franklin

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=20140124192343.GP30525@edge \
    --to=denys@ti.com \
    --cc=fcooper@ti.com \
    --cc=meta-arago@arago-project.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.