From: Mike Frysinger <vapier@gentoo.org>
To: ltp-list@lists.sourceforge.net
Cc: Mark Ver <markver@us.ibm.com>
Subject: Re: [LTP] hardware requirements
Date: Fri, 24 Jul 2009 21:13:35 -0400 [thread overview]
Message-ID: <200907242113.36309.vapier@gentoo.org> (raw)
In-Reply-To: <OFE8FAC2C8.7B8ECD5A-ON852575FD.0081EDEC-852575FD.00837054@us.ibm.com>
[-- Attachment #1.1: Type: text/plain, Size: 914 bytes --]
On Friday 24 July 2009 19:55:39 Mark Ver wrote:
> Is there an agreed upon set of hardware requirements (memory, disk space,
> etc.) for running, if not all tests, at least the default testcases
> executed by runltp?
not really
> Also, if not very knowledgeable of hardware, is there an easy way to tell
> if a particular test will run on a target platform or not? For example, I
> suspect the DMA_THREAD_DIOTEST7 tests are not expected to run on all
> architectures. Is there a way to find out what platforms it does support?
many of test cases dont care at all about resources. might be useful to have
an embedded doc format so tests that do care about resources can declare them
and then a script can run periodically to collect all of them in a summary
format.
i'm pretty sure that in the vast majority of cases, the memory size is the
only thing that a test may play with.
-mike
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 79 bytes --]
------------------------------------------------------------------------------
[-- Attachment #3: Type: text/plain, Size: 155 bytes --]
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2009-07-25 1:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-24 23:55 [LTP] hardware requirements Mark Ver
2009-07-25 1:13 ` Mike Frysinger [this message]
2009-07-25 3:15 ` Mark Ver
2009-07-25 4:38 ` Henry Yei
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=200907242113.36309.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=ltp-list@lists.sourceforge.net \
--cc=markver@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox