<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="x_x_appendonsend" style="color: inherit;"></div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
Hi Patrick, </div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
Please find my responses inline. I am submitting an updated patch based on your comments.</div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
Regards,</div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
Gnanesh</div>
<hr style="direction: ltr; display: inline-block; width: 98%;">
<div id="x_x_divRplyFwdMsg" dir="ltr" style="color: inherit;"><span style="font-family: Calibri, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);"><b>From:</b> Patrick Robb <probb@iol.unh.edu><br>
<b>Sent:</b> Friday, November 1, 2024 3:45 AM<br>
<b>To:</b> Gnanesh Kambalu Palanethra <gpalanethra@marvell.com><br>
<b>Cc:</b> dts@dpdk.org <dts@dpdk.org>; JogaRao Nartu <njogarao@marvell.com>; Bharath Rajendra <brajendra@marvell.com>; Cody Cheng <ccheng@iol.unh.edu>; Hiral Shah <hshah@marvell.com>; Jerin Jacob <jerinj@marvell.com><br>
<b>Subject:</b> [EXTERNAL] Re: [PATCH 1/1] Cn10K crypto Tests: Added Marvell Cn10K specific crypto Tests to TestCryptoPerfCryptodevPerf</span>
<div> </div>
</div>
<div dir="ltr" lang="en" id="x_x_x_pfptBanneryx2joz4" style="background-color: rgb(210, 208, 208); visibility: visible !important; opacity: 1 !important; max-width: none !important; max-height: none !important; display: block !important; text-align: left !important; margin: 16px 0px !important; padding: 8px 16px !important; border-radius: 4px !important; min-width: 200px !important; border-top: 4px solid rgb(141, 140, 140) !important; color: inherit;">
<div id="x_x_x_pfptBanneryx2joz4" style="background-color: rgb(210, 208, 208); visibility: visible !important; opacity: 1 !important; max-height: none !important; float: left !important; display: block !important; margin: 0px 0px 1px !important; max-width: 600px !important; color: inherit;">
<div id="x_x_x_pfptBanneryx2joz4" style="background-color: rgb(210, 208, 208); color: rgb(0, 0, 0); opacity: 1 !important; max-width: none !important; max-height: none !important; display: block !important; visibility: visible !important; font-family: Arial, sans-serif !important; font-weight: bold !important; font-size: 14px !important; line-height: 18px !important;">
Prioritize security for external emails:</div>
<div id="x_x_x_pfptBanneryx2joz4" style="font-weight: normal; background-color: rgb(210, 208, 208); color: rgb(0, 0, 0); opacity: 1 !important; max-width: none !important; max-height: none !important; display: block !important; visibility: visible !important; font-family: Arial, sans-serif !important; font-size: 12px !important; line-height: 18px !important; margin-top: 2px !important;">
Confirm sender and content safety before clicking links or opening attachments</div>
</div>
<div id="x_x_x_pfptBanneryx2joz4" style="background-color: rgb(210, 208, 208); visibility: visible !important; opacity: 1 !important; max-width: none !important; max-height: none !important; float: right !important; display: block !important; margin: 0px 0px 0px 16px !important; text-align: right !important; width: fit-content !important; color: inherit;">
<div style="white-space: nowrap; margin: 3px 0px 3px 16px; padding: 7.5px 16px; border-width: 1px; border-style: solid; border-color: rgb(102, 102, 102); border-radius: 2px; display: inline-block; font-family: Arial, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">
<span style="background-color: rgb(210, 208, 208);"><a href="https://us-phishalarm-ewt.proofpoint.com/EWT/v1/CRVmXkqW!uK3X-9Acabm2WiDRsTBS4rIwIvRbVjipps-cHL1rcSsoqDSFNMcXqr8BOINoBweI4pZ27nz0d8jq5OKeirZIB_d-hHWPT7z2gNmL_lMlHhGml7DuPSnMefWOSbKR7Q$" id="OWA86488cb9-29ec-41a7-d2c2-ecd6693ad2e0" class="x_x_OWAAutoLink" data-auth="NotApplicable" style="text-decoration: none; display: inline-block; background-color: rgb(210, 208, 208); max-width: none; max-height: none;">Report Suspicious</a></span></div>
</div>
<div style="line-height: 0; display: block; font-size: 0.01px;"> </div>
</div>
<div style="direction: ltr;">Hi Gnanesh, thanks for sending this. My name is Patrick Robb, and I'm a CI Testing Lab manager at the DPDK Community Lab hosted at UNH, and a maintainer for the "new" DTS framework which exists within the DPDK repo and should be
replacing the legacy DTS project in the long term(what this patch is for). We do have a Marvell CN10K board at the lab, and I would love to begin running some crypto testing from that if possible (so, thanks again for this series). </div>
<div style="direction: ltr;"><br>
</div>
<div style="direction: ltr;">So, most likely we will want to provide a review from UNH and test this, so that it can be merged to DTS (technically I was granted the authority to apply patches to the legacy repo).</div>
<div style="direction: ltr;"><br>
</div>
<div style="direction: ltr;">I am adding Cody to this thread as I think he can assist me on this. Cody I am going to provide some comments inline as an initial review for this series, and then we should apply this series locally on the traffic generator/test
engine for the CN10K (Intel-1 in our lab), dry run the test which Gnanesh has added, and report back to him. If all goes well, it should be possible to merge. </div>
<div style="direction: ltr;"><br>
</div>
<div style="direction: ltr;">Long term, we will want to circle back and add this test to the new DTS framework, but it is not ready for this test yet, as currently new DTS is testpmd only - there is not cryptodev support. Although, adding such support to new
DTS is something I would love to work with you on in the next year if you have time available for development towards DPDK testing! Anyways, comments inline:</div>
<div style="direction: ltr;"><br>
</div>
<div style="direction: ltr;">On Wed, Oct 30, 2024 at 12:44 PM Gnanesh <<a href="mailto:gpalanethra@marvell.com" id="OWAa23206dd-c97c-94e6-aa91-35d6703cd793" class="x_x_OWAAutoLink">gpalanethra@marvell.com</a>> wrote:</div>
<blockquote style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left: 1px solid rgb(204, 204, 204);">
<div style="direction: ltr;"> Changes included in this patch:<br>
-- New TestCases are added for Cn10K CPT Hardware crypto accelerator.<br>
-- when Testing newly added Testcases it is found Necessary to make Below Changes<br>
1> tests/cryptodev_common.py<br>
--> bind_qat_device function is updated to generate VFs for the given crypto_dev_id<br>
--> added New function bind_mrvl_devices to accept list of PCI Ids and bind it to vfio_pci driver.<br>
2> framework/crb.py<br>
--> updated pci_devices_information_uncached_linux Method to handle additional Nic Speeds for Cavium,<br>
as it was restricting only to 1 GIG NIC speed</div>
</blockquote>
<div style="direction: ltr;"><br>
</div>
<div style="direction: ltr;">Thanks, I also made this change on our local DTS project for cn10k, but the patch was not submitted to the "legacy DTS" mailing list here as it was unmaintained (and still is, to David's point). But, if we can do a review it is
good to get these things into mainline. Maybe I can rebase our local patch on yours if there were any other changes, and get feedback for cn10k specific questions.</div>
<div style="direction: ltr;"><br>
</div>
<div style="direction: ltr;">I have a hard time understanding how this 10G NIC speed requirement got added in the first place as it was quite peculiar and confused me for a time as it was dropping the ports list! I'm sure you had a similar experience... :)</div>
<div style="direction: ltr;"> </div>
<blockquote style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left: 1px solid rgb(204, 204, 204);">
<div style="direction: ltr;"> 3> framework/settings.py<br>
--> Changed the default Cavium NIC driver to rvu_nicpf.</div>
</blockquote>
<div style="direction: ltr;"><br>
</div>
<div style="direction: ltr;">Thanks, we are also running from this change at the Community Lab. But, I thought you said above you are creating VFs from the bind_qat_device function. So, does rvu_nicvf need to be added as well?</div>
<div style="direction: ltr;"> </div>
<blockquote style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left: 1px solid rgb(204, 204, 204);">
<div style="direction: ltr;"> 4> nics/net_device.py<br>
--> added Missing expect object<br>
5> conf/crypto_perf_cryptodev_perf.cfg<br>
--> added Marvell Cn10K configs for crypto_perf_cryptodev_perf<br>
6> framework/ssh_pexpect.py<br>
--> output.replace command's output is not set before returning from get_output_all method<br>
hence Unnecessarily returning Prompt along with the output<br>
7> tests/TestSuite_crypto_perf_cryptodev_perf.py<br>
--> added Marvell CN10K Testcases</div>
</blockquote>
<div style="direction: ltr;"><br>
</div>
<div style="direction: ltr;">Again we will apply these, give them a run, and report back.</div>
<div style="direction: ltr;"> </div>
<blockquote style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left: 1px solid rgb(204, 204, 204);">
<div style="direction: ltr;"> Updated Below Private functions<br>
6.1> _run_crypto_perf() --> receives additional KW arguments<br>
6.2> _parse_output() ---> Updated to handle Marvell Cn10K app command output<br>
6.3> _run_crypto_perf_throughput() --> receives additional KW arguments</div>
</blockquote>
<div style="direction: ltr;"><br>
</div>
<div style="direction: ltr;"><br>
</div>
<div style="direction: ltr;">I don't see any modifications for the build process. Is there a need to include "-Dplatform=cn10k" when setting up the build from meson, or is the default build fine?</div>
<div style="direction: ltr;"><br>
</div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(12, 100, 192);">
right now there is no change to build procedure, we are cross compiling DPDK on x86 and copying the application on to DUT.</div>
<div style="direction: ltr;"><br>
</div>
<div style="direction: ltr;"><br>
</div>
<div style="direction: ltr;"> </div>
<blockquote style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left: 1px solid rgb(204, 204, 204);">
<div style="direction: ltr;"><br>
<br>
Signed-off-by: Gnanesh <<a href="mailto:gpalanethra@marvell.com" id="OWA3e43a8a5-c7c1-4790-49a5-f45586f04bb1" class="x_x_OWAAutoLink">gpalanethra@marvell.com</a>><br>
---<br>
conf/crypto_perf_cryptodev_perf.cfg | 849 ++++++++++++++++++<br>
framework/crb.py | 6 +-<br>
framework/settings.py | 4 +-<br>
framework/ssh_pexpect.py | 2 +-<br>
nics/net_device.py | 3 +<br>
tests/TestSuite_crypto_perf_cryptodev_perf.py | 322 ++++++-<br>
tests/cryptodev_common.py | 11 +-<br>
7 files changed, 1172 insertions(+), 25 deletions(-)<br>
<br>
diff --git a/framework/crb.py b/framework/crb.py<br>
index 9e3b0a58..2fe9d147 100644<br>
--- a/framework/crb.py<br>
+++ b/framework/crb.py<br>
@@ -374,15 +374,15 @@ class Crb(object):<br>
pass<br>
<br>
for i in range(len(match)):<br>
- # check if device is cavium and check its linkspeed, append only if it is 10G<br>
+ # for cavium supported link speed specfied under linkspeeds<br>
if "177d:" in match[i][1]:<br>
- linkspeed = "10000"<br>
+ linkspeeds = ["40000", "10000", "25000", "50000", "100000"]</div>
</blockquote>
<div style="direction: ltr;"><br>
</div>
<div style="direction: ltr;">Honestly I don't understand why we have this condition at all. Other devices in DTS do not have this check where the portlinks can be dropped in crbs.py. What do you think about updating the accepted linkspeeds vs just removing
this step entirely? Can we expect additional linkspeeds to be added for 177d in the future, and have this problem crop up again for a new linkspeed, or is this list of speeds "final" for 177d?</div>
<div style="direction: ltr;"><br>
</div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(12, 100, 192);">
This check is now completely Removed in the updated patch.</div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr;"> </div>
<blockquote style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left: 1px solid rgb(204, 204, 204);">
<div style="direction: ltr;"> nic_linkspeed = self.send_expect(<br>
"cat /sys/bus/pci/devices/%s/net/*/speed" % match[i][0],<br>
"# ",<br>
alt_session=True,<br>
)<br>
- if nic_linkspeed.split()[0] == linkspeed:<br>
+ if nic_linkspeed.split()[0] in linkspeeds:<br>
self.pci_devices_info.append((match[i][0], match[i][1]))<br>
else:<br>
self.pci_devices_info.append((match[i][0], match[i][1]))<br>
diff --git a/framework/settings.py b/framework/settings.py<br>
index 1a561dda..b2c371f8 100644<br>
--- a/framework/settings.py<br>
+++ b/framework/settings.py<br>
@@ -166,8 +166,8 @@ DRIVERS = {<br>
"cavium_a034": "thunder-nicvf",<br>
"cavium_0011": "thunder-nicvf",<br>
"IXGBE_10G-X550EM_X_SFP": "ixgbe",<br>
- "cavium_a063": "octeontx2-nicpf",<br>
- "cavium_a064": "octeontx2-nicvf",<br>
+ "cavium_a063": "rvu_nicpf",<br>
+ "cavium_a064": "rvu_nicvf",</div>
</blockquote>
<div style="direction: ltr;"><br>
</div>
<div style="direction: ltr;">Okay disregard my comment from above about nicvf, I see you've added it. Please do update the commit message to reflect that this is included. And, while you're at it, you can update the commit message to accord with the style guidelines
for submitting DPDK patches as seen here on sections 9.6 and 9.7 <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__doc.dpdk.org_guides_contributing_patches.html&d=DwMFaQ&c=nKjWec2b6R0mOyPaz7xtfQ&r=Ulaoc1LiTkE5RG69cLkMa7P9xGTL0rP6LosuDS8KOe4&m=yMQuTxirxlDswEOgMtDRf6ZbKP5WHuwmlCh4L0OD2_SRTpFWN13r2mHGaVw79Yld&s=0zOdBmtI06ggYRLG6hM42PANpPCDOtwFmFz5EWUKVAw&e=" id="OWAf04c0f81-3d7c-a9a8-c414-e5acbc5a8e47" class="x_x_OWAAutoLink" data-auth="NotApplicable">
https://doc.dpdk.org/guides/contributing/patches.html</a></div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(12, 100, 192);">
<br>
</div>
<div class="elementToProof" style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(12, 100, 192);">
This change message is already part of the commit message. </div>
<div class="elementToProof" style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(12, 100, 192);">
Regarding the style guideline, I have tried to incorporate in the updated patch, please help me in case further changes are needed</div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="direction: ltr;"> </div>
<div style="direction: ltr;">:)</div>
<div style="direction: ltr;"><br>
</div>
<blockquote style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left: 1px solid rgb(204, 204, 204);">
<div style="direction: ltr;"> "ICE_100G-E810C_QSFP": "ice",<br>
"ICE_25G-E810C_SFP": "ice",<br>
"ICE_25G-E823C_QSFP": "ice",<br>
diff --git a/framework/ssh_pexpect.py b/framework/ssh_pexpect.py<br>
index 2132c066..a96087d2 100644<br>
--- a/framework/ssh_pexpect.py<br>
+++ b/framework/ssh_pexpect.py<br>
@@ -186,7 +186,7 @@ class SSHPexpect:<br>
<br>
def get_output_all(self):<br>
output = self.session.before<br>
- output.replace("[PEXPECT]", "")<br>
+ output = output.replace("[PEXPECT]#", "")</div>
</blockquote>
<div style="direction: ltr;"><br>
</div>
<div style="direction: ltr;">So, this is just removing the leading "#" from the output? I'm not sure we should be making styling changes for a "deprecated" repository. If I look at this example output, from one of the CI runs of this testsuite on a quickassist
card: </div>
<div style="direction: ltr;"><br>
</div>
<div style="direction: ltr;"># Device 1 on lcore 40<br>
<br>
# total operations: 30000000<br>
# Buffer size: 1024<br>
# Burst size: 32<br>
# Number of bursts: 937500<br>
#<br>
# Total Average Maximum Minimum<br>
# enqueued 30000000 32 32 32<br>
# dequeued 30000000 32 32 1<br>
# cycles 91892876610 3063 304625 485<br>
# time [us] 3675715064 122.520 12185.000 19.400</div>
<div style="direction: ltr;"><br>
</div>
<div style="direction: ltr;">I imagine the DTS maintainers were aware of this and thought it was the most clear way to print the logs. I don't think we need to override that decision now.</div>
<div style="direction: ltr;"><br>
</div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(12, 100, 192);">
This is not a styling change.</div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(12, 100, 192);">
output.replace will not replace the special prompt "[PEXPECT]" directly on the variable.</div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(12, 100, 192);">
output variable needs to be overwritten to have the output strip of the prompt [I am overwriting output ]</div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(12, 100, 192);">
special prompt variable is "[PEXPECT]#", not the "[PEXPECT]". hence output will have unwanted "#" string. </div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
</div>
<div style="direction: ltr;"> </div>
<div style="direction: ltr;"><br>
</div>
<blockquote style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left: 1px solid rgb(204, 204, 204);">
<div style="direction: ltr;"> return output<br>
<br>
def close(self, force=False):<br>
diff --git a/nics/net_device.py b/nics/net_device.py<br>
index 0f9c1af4..dd0d0e92 100644<br>
--- a/nics/net_device.py<br>
+++ b/nics/net_device.py<br>
@@ -43,6 +43,7 @@ class NetDevice(object):<br>
if not isinstance(crb, Crb):<br>
raise Exception(" Please input the instance of Crb!!!")<br>
self.crb = crb<br>
+ self.__send_expect = self.crb.send_expect<br>
self.domain_id = domain_id<br>
self.bus_id = bus_id<br>
self.devfun_id = devfun_id<br>
@@ -727,6 +728,8 @@ class NetDevice(object):<br>
"/sys/bus/pci/devices/%s:%s:%s" % (domain_id, bus_id, devfun_id),<br>
vf_reg_file,<br>
)<br>
+ self.__send_expect("echo 0 > %s" %<br>
+ (vf_reg_path), "# ")</div>
</blockquote>
<div style="direction: ltr;"><br>
</div>
<div style="direction: ltr;">So, the pre-existing VFs need to be destroyed before a new set of VFs can be created? Do you know if this is Marvell specific, or a universal behavior? </div>
<div style="direction: ltr;"><br>
</div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(12, 100, 192);">
I am not aware of the other boards, but it is the clean way of creating the VFs. </div>
<div style="direction: ltr;"> </div>
<blockquote style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left: 1px solid rgb(204, 204, 204);">
<div style="direction: ltr;"> self.__send_expect("echo %d > %s" % (int(vf_num), vf_reg_path), "# ")<br>
<br>
def generate_sriov_vfs_linux_igb_uio(self, domain_id, bus_id, devfun_id, vf_num):<br>
diff --git a/tests/TestSuite_crypto_perf_cryptodev_perf.py b/tests/TestSuite_crypto_perf_cryptodev_perf.py<br>
index a3f48eee..b435cefa 100644<br>
--- a/tests/TestSuite_crypto_perf_cryptodev_perf.py<br>
+++ b/tests/TestSuite_crypto_perf_cryptodev_perf.py<br>
@@ -59,14 +59,74 @@ class TestCryptoPerfCryptodevPerf(TestCase):<br>
"# ",<br>
5,<br>
)<br>
-<br>
- cc.bind_qat_device(self, "vfio-pci")<br>
+ if self.nic == "cavium_a063":<br>
+ count = len(self.get_suite_cfg().get('l').split(",")) - 1<br>
+ cc.bind_qat_device(self, "vfio-pci", generate_vfs=True, vf_count=count)<br>
+ else:<br>
+ cc.bind_qat_device(self, "vfio-pci")</div>
</blockquote>
<div style="direction: ltr;"><br>
</div>
<div style="direction: ltr;">If we are going to use this function for non-QAT devices, can we please update the function name to prevent confusion? It looks like it's a short list:</div>
<div style="direction: ltr;"><br>
</div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(12, 100, 192);">
Addressed this in the updated patch</div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr;">probb@d121003:~/repos/dts> grep -r "bind_qat_d" .<br>
./tests/TestSuite_compressdev_qat_pmd.py: cc.bind_qat_device(self, self.drivername)<br>
./tests/TestSuite_crypto_perf_cryptodev_perf.py: cc.bind_qat_device(self, "vfio-pci")<br>
./tests/TestSuite_fips_cryptodev.py: cc.bind_qat_device(self, "vfio-pci")<br>
./tests/TestSuite_ipsec_gw_cryptodev_func.py: cc.bind_qat_device(self, self.drivername)<br>
./tests/TestSuite_l2fwd_cryptodev_func.py: cc.bind_qat_device(self, self.drivername)<br>
./tests/TestSuite_virtio_ipsec_cryptodev_func.py: cc.bind_qat_device(self, self.drivername)<br>
./tests/TestSuite_virtio_perf_cryptodev_func.py: cc.bind_qat_device(self, self.drivername)<br>
./tests/TestSuite_virtio_unit_cryptodev_func.py: cc.bind_qat_device(self, self.drivername)<br>
./tests/compress_common.py:def bind_qat_device(test_case, driver="igb_uio"):<br>
./tests/cryptodev_common.py:def bind_qat_device(test_case, driver="igb_uio"):</div>
<div style="direction: ltr;"><br>
</div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(12, 100, 192);">
<br>
</div>
<div style="direction: ltr;"> </div>
<blockquote style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left: 1px solid rgb(204, 204, 204);">
<div style="direction: ltr;"> src_files = ["dep/test_aes_cbc.data", "dep/test_aes_gcm.data"]<br>
self.dut_file_dir = "/tmp"<br>
for file in src_files:<br>
self.dut.session.copy_file_to(file, self.dut_file_dir)<br>
<br>
def tear_down_all(self):<br>
+ if self.nic == "cavium_a063":<br>
+ cc.bind_qat_device(self, "vfio-pci", generate_vfs=True,<br>
+ vf_count=2)<br>
+ import pandas as pd</div>
</blockquote>
<div style="direction: ltr;"><br>
</div>
<div style="direction: ltr;">I don't have a problem with this, but I'm just wondering why this is imported here as opposed to the top of the file?</div>
<div style="direction: ltr;"><br>
</div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(12, 100, 192);">
wrt to pandas import, as we are generating this report only in Marvell case. this import should not affect others</div>
<div style="direction: ltr;"> </div>
<blockquote style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left: 1px solid rgb(204, 204, 204);">
<div style="direction: ltr;">+ tuples = [('TestCase',), ('performance', 'failed_enq'),<br>
+ ('performance', 'failed_deq'),<br>
+ ('performance', 'throughput_mops'),<br>
+ ('performance', 'cycle_buf'),<br>
+ ('performance', 'throughput', 'value'),<br>
+ ('performance', 'throughput', 'delta'),<br>
+ ('parameters', 'core_num/thread_num'),<br>
+ ('parameters', 'frame_size'),<br>
+ ('parameters', 'burst_size'),<br>
+ ('parameters', 'total_ops'), ('status',)]<br>
+ mindex = pd.MultiIndex.from_tuples(tuples)<br>
+ index = 0<br>
+ df = pd.DataFrame([], columns=mindex)<br>
+ for tname, data in self._perf_result.items():<br>
+ for dt in data:<br>
+ for key, value in dt.items():<br>
+ df.loc[index, 'TestCase'] = tname<br>
+ if key == 'status':<br>
+ df.loc[index, (key)] = value<br>
+ continue<br>
+ for item in value:<br>
+ if item['name'] == 'throughput':<br>
+ df.loc[index, (key, item['name'], 'value')] = item['value']<br>
+ df.loc[index, (key, item['name'], 'delta')] = item['delta']<br>
+ else:<br>
+ df.loc[index, (key, item['name'])] = item['value']<br>
+ index += 1<br>
+ perf_xl = self.logger.log_path + "/" + "perf_cryptodev_result.xls"<br>
+ writer = pd.ExcelWriter(perf_xl, engine='xlsxwriter')<br>
+ wb = writer.book<br>
+ df.to_excel(writer, sheet_name='Sheet1')<br>
+ ws = writer.sheets["Sheet1"]<br>
+ merge_format = wb.add_format({"bold": 1,"border": 1,"align": "center",<br>
+ "valign": "vcenter"})<br>
+ ws.merge_range('B1:B3', "TestCase", merge_format)<br>
+ ws.merge_range('C2:C3', "failed_enq", merge_format)<br>
+ ws.merge_range('D2:D3', "failed_deq", merge_format)<br>
+ ws.merge_range('E2:E3', "throughput_mops", merge_format)<br>
+ ws.merge_range('F2:F3', "throughput_mops", merge_format)<br>
+ ws.merge_range('I2:I3', "core_num/thread_num", merge_format)<br>
+ ws.merge_range('J2:J3', "frame_size", merge_format)<br>
+ ws.merge_range('K2:K3', "burst_size", merge_format)<br>
+ ws.merge_range('L2:L3', "total_ops", merge_format)<br>
+ ws.merge_range('M1:M3', "status", merge_format)<br>
+<br>
+ format1 = wb.add_format({"bg_color": "#C6EFCE", "font_color": "#006100", "border": 1})<br>
+ format2 = wb.add_format({"bg_color": "#FFC7CE", "font_color": "#9C0006"})<br>
+ ws.conditional_format("B1:M3", {"type": "cell", "criteria": ">=", "value": 0 , 'format': format2})<br>
+ condition = 'B5:M%s'%(5+len(df)-1)<br>
+ ws.conditional_format(condition, {'type': 'no_blanks', 'format':format1})<br>
+ ws.autofit()<br>
+<br>
+ wb.close()<br>
if self._perf_result:<br>
with open(<br>
self.logger.log_path + "/" + "perf_cryptodev_result.json", "a"<br>
@@ -175,12 +235,197 @@ class TestCryptoPerfCryptodevPerf(TestCase):<br>
def test_scheduler_zuc(self):<br>
self._run_crypto_perf_throughput()<br>
<br>
+ # Marvell CN10K Testcases<br>
+ def _crypto_func_cn10k(self):<br>
+ """Functional tests Helper<br>
+ Returns:<br>
+ None<br>
+ """<br>
+ self._run_crypto_func()<br>
+<br>
+ def _crypto_perf_cn10k(self):<br>
+ """Perf tests Helper function<br>
+ Returns:<br>
+ None<br>
+ """<br>
+ self._run_crypto_perf_throughput(expected="# ",<br>
+ trim_whitespace=False)<br>
+ def test_perf_mrvl_aes_cbc(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_aes_gcm_encrypt(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_aes_cbc_cipher_then_auth(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_aes_sha2_256_cipher_then_auth(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_zuc_eea3_cipher_only(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_zuc_eia3_auth_only(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_aes_gmac_auth_only(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_null_cipher_only(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_snow3g_uea2_cipher_only(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_kasumi_f8_cipher_only(self):<br>
+ self._crypto_perf_cn10k() #F<br>
+<br>
+ def test_perf_mrvl_snow3g_uia2_auth_only(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_kasumi_f9_auth_only(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_sha1_hmac_auth_only(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_sha1_auth_only(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_aes_ctr_cipher_then_auth(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_aes_ctr_snow_3g_uia2_cipher_then_auth(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_aes_cmac_cipher_then_auth(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_3des_cbc_cipher_then_auth(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_sha1_hmac_cipher_then_auth(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_sha2_224_hmac_cipher_then_auth(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_sha2_256_hmac_cipher_then_auth(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_sha2_384_hmac_cipher_then_auth(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_aes_ctr_snow_3g_uia2_cipher_then_auth(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_aes_ctr_zuc_eia3_cipher_then_auth(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_aes_ctr_aes_cmac_cipher_then_auth(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_zuc_eea3_snow3g_uia2_cipher_then_auth(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_zuc_eea3_zuc_eia3_cipher_then_auth(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_zuc_eea3_aes_cmac_cipher_then_auth(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_snow3g_uea2_snow3g_uia2_cipher_then_auth(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_snow3g_uea2_zuc_eia3_cipher_then_auth(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_snow3g_uea2_aes_cmac_cipher_then_auth(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_md5_hmac_auth_only(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_aes_ctr_cipher_only(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_3des_cbc_cipher_only(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_sha2_224_hmac_auth_only(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_sha2_256_hmac_auth_only(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_sha2_384_hmac_auth_only(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_sha2_512_hmac_auth_only(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_aes_xts__cipher_only(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_des_cbc_cipher_only(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_md5_auth_only(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_sha512_auth_only(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_sha384_auth_only(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_sha256_auth_only(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_sha224_auth_only(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_snow3g_uea2_snow3g_uia2(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_sha1_hmac_armv8(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_perf_mrvl_sha2_hmac_armv8(self):<br>
+ self._crypto_perf_cn10k()<br>
+<br>
+ def test_mrvl_ptest(self):<br>
+ self._crypto_func_cn10k()<br>
+<br>
+ def test_mrvl_burst(self):<br>
+ self._crypto_func_cn10k()<br>
+<br>
+ def test_mrvl_devtype(self):<br>
+ self._crypto_func_cn10k()<br>
+<br>
+ def test_mrvl_crypto_sha1_hmac_armv8(self):<br>
+ self._crypto_func_cn10k()<br>
+<br>
+ def test_mrvl_chacha20_poly1305_aead(self):<br>
+ self._crypto_func_cn10k()<br>
+<br>
+ def test_mrvl_crypto_sha2_hmac_armv8(self):<br>
+ self._crypto_func_cn10k()<br>
+<br>
+ def test_mrvl_buffer(self):<br>
+ self._crypto_func_cn10k()<br>
+<br>
# Private functions<br>
def _run_crypto_func(self):<br>
+ """ Runs Crypto functional test.<br>
+ Returns:<br>
+ None<br>
+ """<br>
+<br>
if cc.is_test_skip(self):<br>
return<br>
-<br>
- cores = ",".join(self.dut.get_core_list("1S/2C/1T"))<br>
+ core_list = self.get_suite_cfg().get('core_list',"1S/2C/1T")<br>
+ cores = ",".join(self.dut.get_core_list(core_list))<br>
config = {"l": cores}<br>
devices = self._get_crypto_device(1)<br>
if not devices:<br>
@@ -206,12 +451,22 @@ class TestCryptoPerfCryptodevPerf(TestCase):<br>
<br>
out = self.dut.send_command(<br>
"cat %s/%s.txt" % (self.dut_file_dir, self.running_case), 30<br>
- )<br>
-<br>
+ ).strip()<br>
self.verify("Error" not in out, "Test function failed")<br>
self.verify("failed" not in out, "Test function failed")<br>
-<br>
- def _run_crypto_perf(self):<br>
+ assert (out != ""), "No output"<br>
+<br>
+ def _run_crypto_perf(self, **kwargs):<br>
+ """ Runs Crypto Performance test.<br>
+ Args:<br>
+ **kwargs:<br>
+ expected: send_expect match prompt<br>
+ trim_whitespace: trime whitespace from command output<br>
+ Returns:<br>
+ None<br>
+ """<br>
+ expected = kwargs.get("expected", "#")<br>
+ trim_whitespace = kwargs.get("trim_whitespace", True)<br>
if cc.is_test_skip(self):<br>
return "skip"<br>
<br>
@@ -222,13 +477,14 @@ class TestCryptoPerfCryptodevPerf(TestCase):<br>
return "skip"<br>
<br>
eal_opt_str = cc.get_eal_opt_str(self, devices)<br>
- crypto_perf_opt_str = self._get_crypto_perf_opt_str()<br>
+ crypto_perf_opt_str = self._get_crypto_perf_opt_str(**kwargs)<br>
<br>
cmd_str = cc.get_dpdk_app_cmd_str(<br>
self._app_path, eal_opt_str, crypto_perf_opt_str<br>
)<br>
try:<br>
- out = self.dut.send_expect(cmd_str, "#", 600)<br>
+ out = self.dut.send_expect(cmd_str, expected, 600,<br>
+ trim_whitespace=trim_whitespace)<br>
except Exception as ex:<br>
self.logger.error(ex)<br>
raise ex<br>
@@ -237,25 +493,44 @@ class TestCryptoPerfCryptodevPerf(TestCase):<br>
<br>
return results<br>
<br>
- def _get_crypto_perf_opt_str(self, override_crypto_perf_opts={}):<br>
+ def _get_crypto_perf_opt_str(self, **kwargs):<br>
+ """get crypto perf app option string<br>
+ args:<br>
+ **kwargs:<br>
+ override_crypto_perf_opts- Suite/Case specfic perf<br>
+ app config to overwrite defaults<br>
+ Returns:<br>
+ crypto perf option string<br>
+ """<br>
+ override_crypto_perf_opts = kwargs.get("override_crypto_perf_opts", {})<br>
return cc.get_opt_str(<br>
self, self._default_crypto_perf_opts, override_crypto_perf_opts<br>
)<br>
<br>
def _parse_output(self, output):<br>
try:<br>
+ dtype = self.get_case_cfg().get('devtype')<br>
+ match_str = r" lcore id|#lcore id"<br>
lines = output.split("\r\n")<br>
line_nb = len(lines)<br>
self.logger.debug("Total output lines: " + str(line_nb))<br>
<br>
for line_index in range(line_nb):<br>
- if lines[line_index].startswith(" lcore id"):<br>
+ if re.match(match_str, lines[line_index]):<br>
self.logger.debug("data output line from: " + str(line_index))<br>
break<br>
- data_line = line_index - 1<br>
+ if dtype == 'crypto_cn10k':<br>
+ data_line = line_index + 2<br>
+ else:<br>
+ data_line = line_index - 1<br>
+<br>
+ if len(lines[data_line].split(","))>1:<br>
+ pattern = re.compile(r',')<br>
+ else:<br>
+ pattern = re.compile(r'\s+')<br>
<br>
results = []<br>
- pattern = re.compile(r"\s+")<br>
+<br>
for line in lines[data_line:-1]:<br>
print(line)<br>
result = {}<br>
@@ -334,9 +609,15 @@ class TestCryptoPerfCryptodevPerf(TestCase):<br>
cpu_info[key] = value.strip()<br>
core, thread = 0, 0<br>
lcores = self.get_case_cfg()["l"].split(",")<br>
+ if 'Core(s) per cluster' in out:<br>
+ cl_soc1 = 'Core(s) per cluster'<br>
+ cl_soc2 = 'Cluster(s)'<br>
+ else:<br>
+ cl_soc1 = 'Core(s) per socket'<br>
+ cl_soc2 = 'Socket(s)'<br>
for lcore in lcores[1:]:<br>
- if int(lcore.strip()) < int(cpu_info["Core(s) per socket"]) * int(<br>
- cpu_info["Socket(s)"]<br>
+ if int(lcore.strip()) < int(cpu_info[cl_soc1]) * int(<br>
+ cpu_info[cl_soc2]<br>
):<br>
core += 1<br>
thread += 1<br>
@@ -362,6 +643,11 @@ class TestCryptoPerfCryptodevPerf(TestCase):<br>
dev = "crypto_snow3g"<br>
elif self.get_case_cfg()["devtype"] == "crypto_zuc":<br>
dev = "crypto_zuc"<br>
+ elif self.get_case_cfg()["devtype"] == "crypto_cn10k":<br>
+ dev = "crypto_cn10k"<br>
+ vf = cc.get_qat_devices(self, cpm_num=1, num=num)<br>
+ device["a"] = ' -a '.join(vf)<br>
+ device["vdev"] = None<br>
elif self.get_case_cfg()["devtype"] == "crypto_scheduler":<br>
dev = "crypto_scheduler"<br>
w = cc.get_qat_devices(self, cpm_num=3, num=num * 3)<br>
@@ -388,8 +674,8 @@ class TestCryptoPerfCryptodevPerf(TestCase):<br>
<br>
return device<br>
<br>
- def _run_crypto_perf_throughput(self):<br>
- results = self._run_crypto_perf()<br>
+ def _run_crypto_perf_throughput(self, **kwargs):<br>
+ results = self._run_crypto_perf(**kwargs)<br>
if results == "skip":<br>
return<br>
self.verify(results, "test results is none, Test Failed")<br>
diff --git a/tests/cryptodev_common.py b/tests/cryptodev_common.py<br>
index b550b468..91067b05 100644<br>
--- a/tests/cryptodev_common.py<br>
+++ b/tests/cryptodev_common.py<br>
@@ -8,7 +8,9 @@ from nics.net_device import GetNicObj<br>
conf = SuiteConf("cryptodev_sample")<br>
<br>
<br>
-def bind_qat_device(test_case, driver="igb_uio"):<br>
+def bind_qat_device(test_case, driver="igb_uio", generate_vfs=False,<br>
+ vf_count=2, drvr_type='generic'):<br>
+<br>
if driver == "vfio-pci":<br>
test_case.dut.send_expect("modprobe vfio", "#", 10)<br>
test_case.dut.send_expect("modprobe vfio-pci", "#", 10)<br>
@@ -38,6 +40,8 @@ def bind_qat_device(test_case, driver="igb_uio"):<br>
devfun_id = addr_array[2]<br>
pf_port = GetNicObj(test_case.dut, domain_id, bus_id, devfun_id)<br>
<br>
+ if generate_vfs:<br>
+ pf_port.generate_sriov_vfs_linux(domain_id, bus_id, devfun_id, vf_count, drvr_type)</div>
</blockquote>
<div style="direction: ltr;"><br>
</div>
<div style="direction: ltr;">Is this different from calling generate_sriov_vfs(), which I assume is the "correct" behavior. There appears to be a common practice in legacy DTS of templating out function names to call instead of using inheritance, so you will
have a base function like bind_port(), and then that templates out calls to bind_port_linux(). bind_port_freebsd(), bind_port_windows() etc. It's a little strange but it is what it is and we should probably stick with the existing system if we are going to
make additions. But, if there is a practical reason why you did it this way, then okay. :)</div>
<div style="direction: ltr;"><br>
</div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(12, 100, 192);">
I missed it initially, addressed it in updated patch.</div>
<div style="direction: ltr;"> </div>
<blockquote style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left: 1px solid rgb(204, 204, 204);">
<div style="direction: ltr;"> sriov_vfs_pci = pf_port.get_sriov_vfs_pci()<br>
if not sriov_vfs_pci:<br>
raise Exception("can not get vf pci")<br>
@@ -51,6 +55,11 @@ def bind_qat_device(test_case, driver="igb_uio"):<br>
<br>
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__test-5Fcase.dev&d=DwMFaQ&c=nKjWec2b6R0mOyPaz7xtfQ&r=Ulaoc1LiTkE5RG69cLkMa7P9xGTL0rP6LosuDS8KOe4&m=yMQuTxirxlDswEOgMtDRf6ZbKP5WHuwmlCh4L0OD2_SRTpFWN13r2mHGaVw79Yld&s=B1TWMhgRG8QFE8zQcOleQ4B7kPHb7NYeTCL2QLkTPaA&e=" id="OWA31bcf00a-3f1b-19df-f800-8994346ace32" class="x_x_OWAAutoLink" data-auth="NotApplicable">test_case.dev</a> =
dev<br>
<br>
+def bind_mrvl_devices(test_case, driver='vfio-pci', **kwargs):<br>
+ pci_list = kwargs.get("pci_list").split()<br>
+ for pci in pci_list:<br>
+ test_case.dut.bind_eventdev_port(driver, pci)<br>
+ return pci_list<br>
<br>
def get_qat_devices(test_case, cpm_num=None, num=1):<br>
if not cpm_num:<br>
--<br>
2.25.1<br>
<br>
</div>
</blockquote>
</body>
</html>