From: Sungho Hong <maverickjin88@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Is it possible to use multiple ip fragmentation table?
Date: Fri, 2 Nov 2018 14:44:42 -0700 [thread overview]
Message-ID: <CAK8vx=hWGfNb-xAjwpbQ5j3F00K6dyVoh+b8pByu7GPKS1=39Q@mail.gmail.com> (raw)
Hello DPDK experts,
I am trying to allocate multiple ip frag table for each rx-queue.
For example,
for loop of rx-queues per logical cores
if ((rxq->frag_tbl = *rte_ip_frag_table_create*(max_flow_num,
IP_FRAG_TBL_BUCKET_ENTRIES, max_flow_num,
frag_cycles,
socket)) == NULL) {
return -1;
}
rxq->pool = *rte_pktmbuf_pool_create*(buf, nb_mbuf, MEMPOOL_CACHE_SIZE,
0, RTE_MBUF_DEFAULT_BUF_SIZE, socket);
for loop end
However I could only create 1 fragmentation table and get the segmentation
fault when I try to allocate the second frag-table for the logical core.
Is it impossible to use multiple frag-table for DPDK?
Because I wanted to avoid a global fragmentation table due to
synchronization issues.
reply other threads:[~2018-11-02 21:44 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='CAK8vx=hWGfNb-xAjwpbQ5j3F00K6dyVoh+b8pByu7GPKS1=39Q@mail.gmail.com' \
--to=maverickjin88@gmail.com \
--cc=users@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).