It's supposed that odp_pmr_terms_avail() returns common number of terms available. But some platform, like keystone, have different number of term entries on different layers, and there is no ability to return correct number. So, in order to be able to figure out exact number of exact PMR terms that available, add argument - PMR term for what the available number is requested.
But, not depending on this change, it's also impossible to know exact number of PMR terms available in case if some PMR, depending on a connection circumstances, can allocate two PMR terms for emulation, actually it will be one PMR, but emulated by two. And implementation cannot know a priori in what circumstances this entry will be used. So, question is open....But, at least, this change allows to return more accurate number. Signed-off-by: Ivan Khoronzhuk <ivan.khoronz...@linaro.org> --- include/odp/api/classification.h | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/include/odp/api/classification.h b/include/odp/api/classification.h index f597b26..3242bf2 100644 --- a/include/odp/api/classification.h +++ b/include/odp/api/classification.h @@ -283,11 +283,13 @@ int odp_cos_pmr_cos(odp_pmr_t pmr_id, odp_cos_t src_cos, odp_cos_t dst_cos); unsigned long long odp_pmr_terms_cap(void); /** - * Return the number of packet matching terms available for use + * Return the number of given packet matching terms available for use + * + * @param[in] term One of the enumerated values supported * * @return A number of packet matcher resources available for use. */ -unsigned odp_pmr_terms_avail(void); +unsigned odp_pmr_terms_avail(odp_pmr_term term); /** * Following structure is used to define composite packet matching rules -- 1.9.1 _______________________________________________ lng-odp mailing list lng-odp@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lng-odp
