From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1074] rte_pktmbuf_pool_create doc reports RTE_SECONDARY as an error but it actually works in a secondary process
Date: Thu, 01 Sep 2022 11:55:44 +0000 [thread overview]
Message-ID: <bug-1074-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=1074
Bug ID: 1074
Summary: rte_pktmbuf_pool_create doc reports RTE_SECONDARY as
an error but it actually works in a secondary process
Product: DPDK
Version: 21.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: doc
Assignee: dev@dpdk.org
Reporter: a.dibacco.ks@gmail.com
Target Milestone: ---
Looking to the rte_pktmbuf_pool_create
(https://doc.dpdk.org/api-21.11/rte__mbuf_8h.html#a593921f13307803b94bbb4e0932db962)
I can see that RTE_SECONDARY is listed among the errors. I tried to use this
function in a secondary and it seems to work fine.
Is it possible that this error reported in the documentation is a leftover from
previous versions?
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2022-09-01 11:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-1074-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/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).