Hi masa,

I also met the second problem you mentioned. Robin from the QE team
fixed it by open the commented code as you did.

Thanks,
Samuel

Masa Murayama wrote:

> Yuan,
> 
> Thank you very much for your answer.
> 
> I have additional two problems on nicdrv. I'll describe them in lines.
> I'm sorry if you are not the right person for the issues.
> 
> ----- Original Message -----
> 
>>Date: Fri, 02 May 2008 11:34:57 +0800
>>From: yf206721 <[EMAIL PROTECTED]>
>>Subject: Re: [driver-discuss] NICDRV Test Suite Released
>>To: Masa Murayama <[EMAIL PROTECTED]>
>>Cc: Alan DuBoff <[EMAIL PROTECTED]>, [email protected],
>>       Jim Walker <[EMAIL PROTECTED]>
>>
>>
>>Masa Murayama 写道:
>>
>>>----- Original Message -----
>>>  
>>>
>>>>Date: Thu, 1 May 2008 00:30:16 -0700 (PDT)
>>>>On Thu, 1 May 2008, Masa Murayama wrote:
>>>>
>>>>    
>>
>>Hi
>>Hi Alan
>>Netperf does not belong to SUN,so we can't open source and deliver it.
>>There are two ways you can got it.
>>1.For internal user,you can add package from 
>>/ws/onnv-stc2/packages/`uname -p`/SUNWstc-netperf2/
>>2.For external user,you can download the netperf source from 
>>http://www.netperf.org and build by yourself.
>>
>>More detail instructions please refer to the NICDRV README
>>http://www.opensolaris.org/os/community/device_drivers/README
>>cheers
>>-yuan.fan
>>
>>>>>Alan,
>>>>>
>>>>>you need put netperf and netserver into both of $NETPERF_HOME and
>>>>>$NETPERF_HOME/amd64 directories for amd64 systems.
>>>>>      
>>>>
>>>>Actually in this case I'm using sparc, but same difference.
>>>>
>>>>    
>>>>
>>>>>It's very stupid behaviour of nicdrv, I think.
>>>>>
> 
> 
> I'm an external user, so I downloaded the original netperf from the url
> above. In the original netperf, the binaries will be installed into 
> single directory. But stf_configure seems to expect netperf binaries are
> installed into two directories, i.e. NETPERF_HOME and NETPERF_HOME/amd64
> for amd64 architecture. Please fix nicdrv to check only NETPERF_HOME
> directory. Or please describe explicitly in README where the netperf
> binaries to be installed.
> 
> 
>>>>>You also need to fix a bug in include/getParameter.ksh I mentioned
>>>>>previously. Make "echo $result" alive in get_default_parameter(),
>>>>>which is currently commented out.
> 
> 
> Just after I installed nicdrv, it didn't work for me. After I investivated
> the behaviour of stf_execute, I found get_default_parameter() in
> getParameter.ksh didn't work correctly. The original code are below.
> Enabling "#       echo $result" line, which was commented out
> in original release, nicdrv worked for me. Is it a bug?
> 
> get_default_parameter() {
> 
>         typeset result=""
> 
>         if [ -n "$DRIVER_NAME" ]; then
>                 result=`get_composite_parameterValue $1 $RUN_MODE $DRIVER_NAME
> `
>         fi
> 
> 
>         if [ -z "${result}" ] && [ -n "$DRIVER_SPEED" ]; then
>                 result=`get_composite_parameterValue $1 $RUN_MODE $DRIVER_SPEE
> D`
>         fi
> 
>         if [ -z "${result}" ] && [ -n "$RUN_MODE" ] ; then
>                 result=`get_composite_parameterValue $1 $RUN_MODE`
>         fi
> 
>         if [ -z "${result}" ]; then
>                 result=`get_simple_parameterValue $1`
>         fi
> 
> #       echo $result
> 
>         if [ -z "$result" ]; then
>                 return 1
>         fi
> }
> 
> Thanks in advance.
> -masa
>  
> 
>>>>>      
>>>>
>>>>I'll go back and look at this.
>>>>
>>>>Where did you get the netperf from? Did you just download it from here:
>>>>
>>>>ftp://ftp.netperf.org/netperf/
>>>>    
>>>
>>>Yes, I downloaded netperf-2.4.4 from above, and just compiled it by myself.
>>>Then I copied netperf and netserver into /usr/local/bin and
>>>/usr/local/bin/amd64.
>>>
>>>-masa
>>>
>>>  
>>>
>>>>I don't know if a specific version is needed or what...there appears to be
> 
>  
> 
>>>>a SUNWstc-netperf2 package and I'm wondering where that is...
>>>>
>>>>--
>>>>
>>>>Alan DuBoff - Solaris x86 IHV/OEM Group
>>>>    
>>>
>>>_______________________________________________
>>>driver-discuss mailing list
>>>[email protected]
>>>http://mail.opensolaris.org/mailman/listinfo/driver-discuss
>>>  
>>
> 
> _______________________________________________
> driver-discuss mailing list
> [email protected]
> http://mail.opensolaris.org/mailman/listinfo/driver-discuss
_______________________________________________
driver-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/driver-discuss

Reply via email to