From: "Qiu, Michael" <michael.qiu@intel.com>
To: "Zhang, XiaonanX" <xiaonanx.zhang@intel.com>,
"Tang, HaifengX" <haifengx.tang@intel.com>,
"dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] dts can not support one more different nics test in one configuration file
Date: Fri, 23 Jan 2015 02:34:46 +0000 [thread overview]
Message-ID: <533710CFB86FA344BFBF2D6802E60286CB8ACF@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <63FB47D6C0357E428AA804B2C89068BA0128F6D0@SHSMSX104.ccr.corp.intel.com>
On 1/22/2015 6:31 PM, Zhang, XiaonanX wrote:
> Hi all,
> When I tested l3fwd performance on the fortville_spirit and fortville_eagle nic on Federal 21 and Federal20,
> I also met this problem.
> I think the question is about framework restore_interfaces function of framework crb.py file and
> I have been modified for fortvill testing due to Fedora20 kernel has been supported i40e driver.
> Suggestion:
> Modifiy /framework/crb.py:
>
> def restore_interfaces(self):
> """
> Restore Linux interfaces.
> """
> if dts.drivername == "vfio-pci":
> self.send_expect("rmmod vfio_iommu_type1", "# ", 10)
> self.send_expect("rmmod vfio_pci", "# ", 10)
> self.send_expect("rmmod vfio", "# ", 10)
> else:
> self.send_expect("rmmod igb_uio", "# ", 10)
> self.send_expect("modprobe igb", "# ", 20)
> self.send_expect("modprobe ixgbe", "# ", 20)
> self.send_expect("modprobe e1000e", "# ", 20)
> self.send_expect("modprobe e1000", "# ", 20)
> self.send_expect("modprobe virtio_net", "# ", 20)
> + self.send_expect("`insmod /usr/lib/modules/`uname -r`/kernel/drivers/net/ethernet/intel/i40e/i40e.ko`", "# ", 50)
If have supported, you should just exec "modprobe i40e" .
Also you need to send out as a patch.
Thanks,
Michael
> It has been verified in our testing performance l3fwd, That's ok.
> But, If we do this We found Fortville testing only run one case, for example L3fwd.
>
> If we run other cases in execution.cfg, such as pmd port map cannot map always -1.
>
>
> Best Regards
> Xiaonan
>
>
>
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Qiu, Michael
> Sent: Thursday, January 22, 2015 3:44 PM
> To: Tang, HaifengX; dts@dpdk.org
> Subject: Re: [dts] dts can not support one more different nics test in one configuration file
>
> On 1/22/2015 3:23 PM, Tang, HaifengX wrote:
>> Hi all:
>> Recently , I found that our dts cannot support one more different nics test in one configuration file.
>> Such as the following configuration:
>>
>> [Execution1]
>> crbs=10.239.128.128
> You'd better to remove this private info in public maillist :)
>
>> drivername=igb_uio
>> test_suites=
>> pmd,
>> ipfrag,
>>
>> targets=
>> x86_64-native-linuxapp-gcc
>> parameters=nic_type=kawela_4:func=true
>>
>> [Execution2]
>> crbs=10.239.128.128
> Here
>
>> drivername=igb_uio
>> test_suites=
>> pmd,
>> ipfrag,
>> targets=
>> x86_64-native-linuxapp-gcc
>> parameters=nic_type=springville:func=true
> BTW, you'd better to supply the error log for others to debug.
>
> Thanks,
> Michael
>> Thanks,
>> Haifeng
>>
>>
>
prev parent reply other threads:[~2015-01-23 2:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 7:22 Tang, HaifengX
2015-01-22 7:39 ` Liu, Yong
2015-01-22 7:44 ` Qiu, Michael
2015-01-22 10:31 ` Zhang, XiaonanX
2015-01-23 2:34 ` Qiu, Michael [this message]
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=533710CFB86FA344BFBF2D6802E60286CB8ACF@SHSMSX101.ccr.corp.intel.com \
--to=michael.qiu@intel.com \
--cc=dts@dpdk.org \
--cc=haifengx.tang@intel.com \
--cc=xiaonanx.zhang@intel.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;
as well as URLs for NNTP newsgroup(s).