d/numam-dpdk
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

net/dpaa: explain behaviour with FMC policy

Browse Source 
This patch adds comment to explain how dpaa_port_fmc_ccnode_parse
function is working to get the HW queue from FMC policy file

Signed-off-by: Rohit Raj <rohit.raj@nxp.com>
Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
This commit is contained in:
Rohit Raj 2021-10-06 22:31:28 +05:30 committed by Thomas Monjalon
parent 89e84deaa5
commit af02d1e2f7
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
drivers/net/dpaa/dpaa_fmc.c
View File

@ -1,5 +1,5 @@
/* SPDX-License-Identifier: BSD-3-Clause
* Copyright 2017-2020 NXP
* Copyright 2017-2021 NXP
*/
/* System headers */
@ -338,6 +338,12 @@ static int dpaa_port_fmc_ccnode_parse(struct fman_if *fif,
fqid = keys_params->key_params[j].cc_next_engine_params
.params.enqueue_params.new_fqid;
/* We read DPDK queue from last classification rule present in
* FMC policy file. Hence, this check is required here.
* Also, the last classification rule in FMC policy file must
* have userspace queue so that it can be used by DPDK
* application.
*/
if (keys_params->key_params[j].cc_next_engine_params
.next_engine != e_IOC_FM_PCD_DONE) {
DPAA_PMD_WARN("FMC CC next engine not support");