All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Hall <mhall-Hv3ogNYU3JfZZajBQzqCxQ@public.gmane.org>
To: "Saha, Avik (AWS)" <aviksaha-vV1OtcyAfmbQT0dZR+AlfA@public.gmane.org>
Cc: "dev-VfR2kkLFssw@public.gmane.org" <dev-VfR2kkLFssw@public.gmane.org>
Subject: Re: LRU using DPDK 1.7
Date: Mon, 22 Sep 2014 22:26:38 -0700	[thread overview]
Message-ID: <20140923052638.GA29592@mhcomputing.net> (raw)
In-Reply-To: <A4A7819F3AE089479B8A88B97202C75D37BE5E49-CFWIZfY9kHlb1ALrAyA8KcFQxgcIjaqzVpNB7YpNyf8@public.gmane.org>

On Tue, Sep 23, 2014 at 03:43:59AM +0000, Saha, Avik (AWS) wrote:

> 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.

I'm referring to the fact that rte_hash'es of all types are kind of 
special-purpose. So it's important to clarify what kind of data you're 
planning to match, using which of the hashes, and which strategy.

In my case I wanted to use them for variable-length data which will likely not 
fit onto a cacheline such as URL's, and they don't work for this application.

Matthew.

      parent reply	other threads:[~2014-09-23  5:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-23  1:08 LRU using DPDK 1.7 Saha, Avik (AWS)
     [not found] ` <A4A7819F3AE089479B8A88B97202C75D37BE5DAA-CFWIZfY9kHlb1ALrAyA8KcFQxgcIjaqzVpNB7YpNyf8@public.gmane.org>
2014-09-23  1:33   ` Matthew Hall
     [not found]     ` <20140923013356.GA26558-Hv3ogNYU3JfZZajBQzqCxQ@public.gmane.org>
2014-09-23  2:42       ` Venkatesan, Venky
2014-09-23  3:43       ` Saha, Avik (AWS)
     [not found]         ` <A4A7819F3AE089479B8A88B97202C75D37BE5E49-CFWIZfY9kHlb1ALrAyA8KcFQxgcIjaqzVpNB7YpNyf8@public.gmane.org>
2014-09-23  5:26           ` Matthew Hall [this message]

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=20140923052638.GA29592@mhcomputing.net \
    --to=mhall-hv3ognyu3jfzzajbqzqcxq@public.gmane.org \
    --cc=aviksaha-vV1OtcyAfmbQT0dZR+AlfA@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.