From: "Saha, Avik (AWS)" <aviksaha@amazon.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Strange behaviour with LRU table
Date: Wed, 24 Sep 2014 23:12:13 +0000 [thread overview]
Message-ID: <A4A7819F3AE089479B8A88B97202C75D37BE8368@ex10-mbx-9001.ant.amazon.com> (raw)
1) All the calls to add entries succeeds
2) The key look up works as expected.
3) The value (entry_data) that is returned is incorrect for every other entry - 1st entry data on .f_action_hit is wrong, 2nd entry_data on .f_action_hit is correct and so on.
I have initialized my LRU as follows:
struct rte_pipeline_table_params table_params = {
.ops = &rte_table_hash_lru_dosig_ops,
.arg_create = &rule_tbl_params,
.f_action_hit = rw_pipeline_stage_2_cache_hit,
.f_action_miss = rw_pipeline_stage_2_cache_miss,
.arg_ah = (void *)lcore_params,
.action_data_size = 16,
};
Is there something obvious I am missing - from first look it seems to be a problem with cache lines but I really am not sure.
Avik
reply other threads:[~2014-09-24 23:06 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=A4A7819F3AE089479B8A88B97202C75D37BE8368@ex10-mbx-9001.ant.amazon.com \
--to=aviksaha@amazon.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).