From: Victor Huertas <vhuertas@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Segmentation fault when creating a hash table in the example of pipeline (ROUTING type)
Date: Thu, 19 Apr 2018 14:33:53 +0200 [thread overview]
Message-ID: <CAGxG5chWM-oWZ49qBvgThv8i4KxaGn+GiVjt=-6A94pEHvnZwQ@mail.gmail.com> (raw)
Hi all,
I have tried to run the pipeline example with a ROUTING pipeline where I
configured n_arp_entries=8 as well as the arp_key_offset = 192.
It compiles perfectly but when it reaches the line where the
rte_pipeline_table_create is (see below a fragment of the source code of
the pipeline_routing_init function at pipeline_routing.be.cpp file) it
always crashes with a segmentation fault at the
rte_table_hash_create_key8_ext() function.
I am completely stuck due to this issue. Has some bug being declared
regarding this table creation function?
/* ARP table configuration */
if (p_rt->params.n_arp_entries) {
struct rte_table_hash_key8_ext_params table_arp_params;
table_arp_params.n_entries = p_rt->params.n_arp_entries;
table_arp_params.n_entries_ext = p_rt->params.n_arp_entries;
table_arp_params.f_hash = hash_default_key8;
table_arp_params.seed = 0;
table_arp_params.signature_offset = 0; /* Unused */
table_arp_params.key_offset = p_rt->params.arp_key_offset;
struct rte_pipeline_table_params table_params = {
.ops = &rte_table_hash_key8_ext_dosig_ops,
.arg_create = &table_arp_params,
.f_action_hit = get_arp_table_ah_hit(p_rt),
.f_action_miss = NULL,
.arg_ah = p_rt,
.action_data_size = sizeof(struct arp_table_entry) -
sizeof(struct rte_pipeline_table_entry),
};
int status;
status = rte_pipeline_table_create(p->p,
&table_params,
&p->table_id[1]);
if (status) {
rte_pipeline_free(p->p);
rte_free(p);
return NULL;
}
p->n_tables++;
}
Thanks
--
Victor
next reply other threads:[~2018-04-19 12:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 12:33 Victor Huertas [this message]
2018-04-19 12:57 ` Shyam Shrivastav
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='CAGxG5chWM-oWZ49qBvgThv8i4KxaGn+GiVjt=-6A94pEHvnZwQ@mail.gmail.com' \
--to=vhuertas@gmail.com \
--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).