From: Li Zefan <lizf@cn.fujitsu.com>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: ltp-list@lists.sourceforge.net,
Frederic Weisbecker <fweisbec@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Eugene Teo <eugene@redhat.com>, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [LTP] [PATCH] Add ftrace-stress-test to LTP
Date: Wed, 25 Aug 2010 10:59:45 +0800 [thread overview]
Message-ID: <4C748721.3020909@cn.fujitsu.com> (raw)
In-Reply-To: <AANLkTi=+8rsbAtHg=N+RCBqDH2W6xD+NVWdXScyJH2Mc@mail.gmail.com>
Garrett Cooper wrote:
> On Tue, Aug 24, 2010 at 6:25 PM, Li Zefan <lizf@cn.fujitsu.com> wrote:
>> Subrata Modak wrote:
>>> Thanks. I need to test this on a suitable kernel. But doubtful if i can
>>> add in the default run.
>>>
>> Why? Because it costs 90 secs? This is configurable, and some other
>> test suites like cpuctl cost more time.
>>
>> If a test suite is not run by default, I guess people won't know its
>> existence, probably.
>
> I think that more of the concern stems from the fact that it's a
> performance test, and a lot of people complain if and when their test
> machines slow down to a halt (take hackbench, proc01, for example).
>
It's not a performance test, but a stress test, which aims at revealing
racy corners in ftrace. Though it will slow down the machine, it won't
halt the machine, unless we hit a serious kernel bug.
> There are issues with the code, but it's dealing with the fact that
> it's not really written in a portable way. Give me a bit of time and
> I'll comment on what needs to be changed.
>
Thanks for reviewing the code. I'm not good at writing protable bash
scripts..
------------------------------------------------------------------------------
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users
worldwide. Take advantage of special opportunities to increase revenue and
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2010-08-25 2:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-24 4:06 [LTP] [PATCH] Add ftrace-stress-test to LTP Li Zefan
2010-08-24 11:02 ` Subrata Modak
2010-08-25 1:25 ` Li Zefan
2010-08-25 2:41 ` Garrett Cooper
2010-08-25 2:59 ` Li Zefan [this message]
2010-09-06 16:16 ` Subrata Modak
2010-09-06 18:52 ` Garrett Cooper
2010-08-25 5:31 ` Garrett Cooper
2010-09-02 1:08 ` Li Zefan
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=4C748721.3020909@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=eugene@redhat.com \
--cc=fweisbec@gmail.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=yanegomi@gmail.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