[parsec-users] parsec-users Digest, Vol 35, Issue 7

Christian Bienia cbienia at CS.Princeton.EDU
Sat Jan 1 17:37:03 EST 2011


Looks like you downloaded only the “core” distribution. If you want
everything, either download the full distribution, or keep what you have
right now and additionally download the two input distributions (depending
what you’d like to do and need).

 

- Chris

 

 

 

From: parsec-users-bounces at lists.cs.princeton.edu
[mailto:parsec-users-bounces at lists.cs.princeton.edu] On Behalf Of ??
Sent: Saturday, January 01, 2011 2:25 PM
To: parsec-users at lists.cs.princeton.edu
Subject: Re: [parsec-users] parsec-users Digest, Vol 35, Issue 7

 

Thank you for the reply

I don't use the native download package, so I don't see the file named
"native.runconf"  in "parsec-2.1/pkgs/dedup/parsec", I can only see the file
"test.runconf" inside the folder. 

The content of "test.runconf" is:

# Binary file to execute, relative to installation root
run_exec="bin/dedup"

# Arguments to use
run_args="-c -p -f -t ${NTHREADS} -i test.dat -o output.dat.ddp"

 I think if I can rename this file to "simsmall.runconf" and set the
"run_args" to the input file "media.dat", so the file "simsmall.runconf"
looks like :

# Binary file to execute, relative to installation root
run_exec="bin/dedup"

# Arguments to use
run_args="-c -p -f -t ${NTHREADS} -i media.dat -o output.dat.ddp"




2011/1/1 <parsec-users-request at lists.cs.princeton.edu>

Send parsec-users mailing list submissions to
       parsec-users at lists.cs.princeton.edu

To subscribe or unsubscribe via the World Wide Web, visit
       https://lists.cs.princeton.edu/mailman/listinfo/parsec-users
or, via email, send a message with subject or body 'help' to
       parsec-users-request at lists.cs.princeton.edu

You can reach the person managing the list at
       parsec-users-owner at lists.cs.princeton.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of parsec-users digest..."

Today's Topics:

  1. Variable 'bench_exec_dedup' for package 'dedup' has       not been
     set (??)
  2. Re: Variable 'bench_exec_dedup' for package 'dedup' has   not
     been set (Yungang Bao)
  3. Re: Variable 'bench_exec_dedup' for package 'dedup'       has     not
     been set (Christian Bienia)


---------- 已转发邮件 ----------
From: 邓宁 <dunning2006 at gmail.com>
To: parsec-users at lists.cs.princeton.edu
Date: Fri, 31 Dec 2010 09:56:02 +0800
Subject: [parsec-users] Variable 'bench_exec_dedup' for package 'dedup' has
not been set
Dear all,

Happy new year!

I install the parsec-2.1-core(49MB) in my machine and build the dedup
benchmark successfully. Then, I want to use a more larger input set, the
simsmall, simmedium and simlarge are simply copied into the input directory.
Also, I copied some *.runconf files into the /config folder in both
"/parsec-2.1/config" and "parsec-2.1/pkgs/dedup/parsec" according to the
prompt from "parsecmgmt". I suppose that the running is OK, but I got an
error saying that "Variable 'bench_exec_dedup' for package 'dedup' has not
been set". 

I found the related location in the parsecmgmt file:

# Determine binary
  local bmexec_suffix=${run_exec}
  if [ -z "${bmexec_suffix}" ]; then
    echo "${oprefix} Variable 'bench_exec_${benchmark}' for package
'${benchmark}' has not been set." | ${TEE} ${log}
    exit 1
  fi
  local bmexec="${bminstdir}/${bmexec_suffix}"
  if [ ! -x "${bmexec}" ]; then
    echo "${oprefix} Error: Binary '${bmexec}' of package '${benchmark}'
cannot be found." | ${TEE} ${log}
    exit 1
  fi


Can anyone tell how I can solve the problem? If I can only run the much
larger input set test by directly copying the input_XXX.tar packages into
the /input folder like I do? Or, I should download the 2.4G full version and
re-build the package from scratch? 

Thank you in advance.

-- 
Regards
Deng Ning (邓 宁)

School Of Computer Science and Technology 
Beijng Institute of Technology, China, 100081
dunning2006 at gmail.com



---------- 已转发邮件 ----------
From: Yungang Bao <ybao at CS.Princeton.EDU>
To: PARSEC Users <parsec-users at lists.cs.princeton.edu>
Date: Thu, 30 Dec 2010 23:13:29 -0500 (EST)
Subject: Re: [parsec-users] Variable 'bench_exec_dedup' for package 'dedup'
has not been set
Hi Ning,

The roles of *.runconf in "/parsec-2.1/config" and
"parsec-2.1/pkgs/dedup/parsec" are different. So you should not copy those
*.runconf in "/parsec-2.1/config" into directory
"parsec-2.1/pkgs/dedup/parsec". Instead, if you want to use different input
size (e.g., simsmall), you should 1) go to directory
"parsec-2.1/pkgs/dedup/parsec", 2) copy "native.runconf" to
"simsmall.runconf" and 3) change run_args from " -i FC-6-x86_64-disc1.iso"
to "-i media.dat".

Best Regards,
Yungang

----- Original Message -----
From: "邓宁" <dunning2006 at gmail.com>
To: parsec-users at lists.cs.princeton.edu
Sent: Thursday, December 30, 2010 8:56:02 PM
Subject: [parsec-users] Variable 'bench_exec_dedup' for package 'dedup' has
not been set


Dear all,

Happy new year!

I install the parsec-2.1-core(49MB) in my machine and build the dedup
benchmark successfully. Then, I want to use a more larger input set, the
simsmall, simmedium and simlarge are simply copied into the input directory.
Also, I copied some *.runconf files into the /config folder in both
"/parsec-2.1/config" and "parsec-2.1/pkgs/dedup/parsec" according to the
prompt from "parsecmgmt". I suppose that the running is OK, but I got an
error saying that "Variable 'bench_exec_dedup' for package 'dedup' has not
been set".

I found the related location in the parsecmgmt file:

# Determine binary
local bmexec_suffix=${run_exec}
if [ -z "${bmexec_suffix}" ]; then
echo "${oprefix} Variable 'bench_exec_${benchmark}' for package
'${benchmark}' has not been set." | ${TEE} ${log}
exit 1
fi
local bmexec="${bminstdir}/${bmexec_suffix}"
if [ ! -x "${bmexec}" ]; then
echo "${oprefix} Error: Binary '${bmexec}' of package '${benchmark}' cannot
be found." | ${TEE} ${log}
exit 1
fi


Can anyone tell how I can solve the problem? If I can only run the much
larger input set test by directly copying the input_XXX.tar packages into
the /input folder like I do? Or, I should download the 2.4G full version and
re-build the package from scratch?

Thank you in advance.

--
Regards
Deng Ning (邓 宁)

School Of Computer Science and Technology
Beijng Institute of Technology, China, 100081
dunning2006 at gmail.com


_______________________________________________
parsec-users mailing list
parsec-users at lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/parsec-users



---------- 已转发邮件 ----------
From: "Christian Bienia" <cbienia at CS.Princeton.EDU>
To: "'PARSEC Users'" <parsec-users at lists.cs.princeton.edu>
Date: Fri, 31 Dec 2010 12:10:10 +0100
Subject: Re: [parsec-users] Variable 'bench_exec_dedup' for package 'dedup'
has not been set
Hi,

Just wanted to add that details about the PARSEC configuration files and the
different variables can be found in the man pages that come with your PARSEC
distribution. We also have them online:

   http://parsec.cs.princeton.edu/doc/man/

Regarding different inputs, you can have any number of inputs for a workload
as long as their names are different. (No need to rename them.) If you
select an input with the `-i XYZ' option, the scripts will look for the
associated XYZ.runconf files.

Best,
Chris


-----Original Message-----
From: parsec-users-bounces at lists.cs.princeton.edu
[mailto:parsec-users-bounces at lists.cs.princeton.edu] On Behalf Of Yungang
Bao
Sent: Friday, December 31, 2010 5:13 AM
To: PARSEC Users
Subject: Re: [parsec-users] Variable 'bench_exec_dedup' for package 'dedup'
has not been set

Hi Ning,

The roles of *.runconf in "/parsec-2.1/config" and
"parsec-2.1/pkgs/dedup/parsec" are different. So you should not copy those
*.runconf in "/parsec-2.1/config" into directory
"parsec-2.1/pkgs/dedup/parsec". Instead, if you want to use different input
size (e.g., simsmall), you should 1) go to directory
"parsec-2.1/pkgs/dedup/parsec", 2) copy "native.runconf" to
"simsmall.runconf" and 3) change run_args from " -i FC-6-x86_64-disc1.iso"
to "-i media.dat".

Best Regards,
Yungang

----- Original Message -----
From: "邓宁" <dunning2006 at gmail.com>
To: parsec-users at lists.cs.princeton.edu
Sent: Thursday, December 30, 2010 8:56:02 PM
Subject: [parsec-users] Variable 'bench_exec_dedup' for package 'dedup' has
not been set


Dear all,

Happy new year!

I install the parsec-2.1-core(49MB) in my machine and build the dedup
benchmark successfully. Then, I want to use a more larger input set, the
simsmall, simmedium and simlarge are simply copied into the input directory.
Also, I copied some *.runconf files into the /config folder in both
"/parsec-2.1/config" and "parsec-2.1/pkgs/dedup/parsec" according to the
prompt from "parsecmgmt". I suppose that the running is OK, but I got an
error saying that "Variable 'bench_exec_dedup' for package 'dedup' has not
been set".

I found the related location in the parsecmgmt file:

# Determine binary
local bmexec_suffix=${run_exec}
if [ -z "${bmexec_suffix}" ]; then
echo "${oprefix} Variable 'bench_exec_${benchmark}' for package
'${benchmark}' has not been set." | ${TEE} ${log}
exit 1
fi
local bmexec="${bminstdir}/${bmexec_suffix}"
if [ ! -x "${bmexec}" ]; then
echo "${oprefix} Error: Binary '${bmexec}' of package '${benchmark}' cannot
be found." | ${TEE} ${log}
exit 1
fi


Can anyone tell how I can solve the problem? If I can only run the much
larger input set test by directly copying the input_XXX.tar packages into
the /input folder like I do? Or, I should download the 2.4G full version and
re-build the package from scratch?

Thank you in advance.

--
Regards
Deng Ning (邓 宁)

School Of Computer Science and Technology
Beijng Institute of Technology, China, 100081
dunning2006 at gmail.com


_______________________________________________
parsec-users mailing list
parsec-users at lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/parsec-users
_______________________________________________
parsec-users mailing list
parsec-users at lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/parsec-users



_______________________________________________
parsec-users mailing list
parsec-users at lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/parsec-users




-- 
Regards
Deng Ning (邓 宁)

School Of Computer Science and Technology 
Beijng Institute of Technology, China, 100081
dunning2006 at gmail.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cs.princeton.edu/pipermail/parsec-users/attachments/20110101/aaea96ef/attachment-0001.html>


More information about the parsec-users mailing list