From: "Saha, Avik (AWS)" <aviksaha@amazon.com>
To: Matthew Hall <mhall@mhcomputing.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] LRU using DPDK 1.7
Date: Tue, 23 Sep 2014 03:43:59 +0000 [thread overview]
Message-ID: <A4A7819F3AE089479B8A88B97202C75D37BE5E49@ex10-mbx-9001.ant.amazon.com> (raw)
In-Reply-To: <20140923013356.GA26558@mhcomputing.net>
So with DPDK 1.7 there are 2 separate implementations - one is the rte_hash which does not support LRU (at least to my understanding - I could be wrong here) and then there is the librte_table library which has support for LRU in a hash table. I m a little confused as to which one you are referring to Matthew.
-----Original Message-----
From: Matthew Hall [mailto:mhall@mhcomputing.net]
Sent: Monday, September 22, 2014 6:34 PM
To: Saha, Avik (AWS)
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] LRU using DPDK 1.7
On Tue, Sep 23, 2014 at 01:08:21AM +0000, Saha, Avik (AWS) wrote:
> I was wondering if there is way to use the rte_table_hash_lru without
> building a pipeline - Basically using the same hash table like
> functionality of add, delete and lookup without setting up a pipeline
> and connect it to ports etc.
I've been finding that rte_hash is designed only for some very specialized purposes. It doesn't work well if you use unexpected sizes of keys or want behavior that isn't precisely doing what the designers of the hash used it for... it's not very general-purpose.
I did try to point out one example of the issue but I didn't get much response yet to my questions about its limitations and whether a more general-purpose table was available, or at least some discussion what rte_hash is for and what it's not for.
Matthew.
next prev parent reply other threads:[~2014-09-23 3:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 1:08 Saha, Avik (AWS)
2014-09-23 1:33 ` Matthew Hall
2014-09-23 2:42 ` Venkatesan, Venky
2014-09-23 3:43 ` Saha, Avik (AWS) [this message]
2014-09-23 5:26 ` Matthew Hall
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=A4A7819F3AE089479B8A88B97202C75D37BE5E49@ex10-mbx-9001.ant.amazon.com \
--to=aviksaha@amazon.com \
--cc=dev@dpdk.org \
--cc=mhall@mhcomputing.net \
/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).