From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] [PATCH] Clear up ambiguity with benchmark instructions.
Date: Fri, 3 Sep 2010 14:55:30 -0400 [thread overview]
Message-ID: <20100903185529.GE3324@Krystal> (raw)
In-Reply-To: <4C8127FD.6090808@ericsson.com>
* Matthew Khouzam (matthew.khouzam at ericsson.com) wrote:
> Thank you Douglas. I feel excessively smart right now.
>
> On 10-09-03 12:44 PM, Douglas Santos wrote:
>> I guess you forgot to send the patch.
>>
>> Quoting Matthew Khouzam<matthew.khouzam at ericsson.com>:
>>
>>
>>> The instructions for the benchmark are a bit ambiguous. The program name
>>> is run and the instruction is run.
>>>
>>> This patch changes the lines to "launch ./run". This way scripts calling
>>> the executable will not have to be patched also.
>>>
>>> _______________________________________________
>>> ltt-dev mailing list
>>> ltt-dev at lists.casi.polymtl.ca
>>> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>>>
>>>
>>
>>
>>
> From 34444ce22297e160bd0e2a80ba645e8f39a7507f Mon Sep 17 00:00:00 2001
> From: root <matthew.khouzam@polymtl.ca>
> Date: Fri, 3 Sep 2010 11:09:29 -0400
> Subject: [PATCH] Author: Matthew Khouzam <matthew.khouzam at polymtl.ca>
> Comments: Several people were confused with the instruction "- run ./run" for the UST benchmark. Changed run to launch
>
> ---
> tests/benchmark/README | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tests/benchmark/README b/tests/benchmark/README
> index 8a9321d..435de86 100644
> --- a/tests/benchmark/README
> +++ b/tests/benchmark/README
> @@ -2,8 +2,8 @@ UST Benchmark
>
> INSTALLATION INSTRUCTIONS:
>
> - - run ./install to install and compile UST/benchmark
> - - run ./run to perform the benchmark
> + - launch ./install to install and compile UST/benchmark
> + - launch ./run to perform the benchmark
Please change to the following and resend the patch:
INSTALLATION INSTRUCTIONS:
Compile and install UST/benchmark with:
% ./install
Launch the benchark with:
% ./run
Here I assume that it is correct to execute these as simple user.
Otherwise, if root access is needed, then change % for #.
Thanks,
Mathieu
>
>
> The trace files will be automatically saved at $HOME/.usttraces
> --
> 1.7.0.4
>
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2010-09-03 18:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 15:31 Matthew Khouzam
[not found] ` <1283532276.4c8125f4633af@www.imp.polymtl.ca>
2010-09-03 16:53 ` Matthew Khouzam
2010-09-03 16:53 ` Matthew Khouzam
2010-09-03 16:53 ` Matthew Khouzam
2010-09-03 18:55 ` Mathieu Desnoyers [this message]
2010-09-03 18:41 ` [ltt-dev] [UST PATCH] " Mathieu Desnoyers
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=20100903185529.GE3324@Krystal \
--to=compudj@krystal.dyndns.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox