DPDK patches and discussions
 help / color / mirror / Atom feed
From: Kamraan Nasim <knasim@sidebandnetworks.com>
To: dev@dpdk.org, "Zhang, Helin" <helin.zhang@intel.com>,
	 Bruce Richardson <bruce.richardson@intel.com>
Cc: Jun Du <jdu@sidebandnetworks.com>
Subject: [dpdk-dev] Changes to 5tuple IPv4 filters in dpdk v2.0
Date: Tue, 4 Aug 2015 16:44:16 -0400	[thread overview]
Message-ID: <CAPrTskjdDc1GPUUSCRjG1r+TjodXXd2+=2J7M6c=jV8+-kpRhA@mail.gmail.com> (raw)

Hi DPDK community,

I've been using DPDK v1.7 and v1.8 for the past year. On updating to
v2.0.0,  I see that *rte_5tuple_filter* has been deprecated as well as the
associated install/remove call,* rte_eth_dev_add_5tuple_filter()*

I now see that rte_eth_ntuple_filter has been added in place.

1) Is there a specific reason for removing backward compatibility? As in is
there a known issue with rte_5tuple_filter infra that was discovered in
v2.0?


2) One limitation of rte_5tuple_filter was that it could not be used to
filter /24 or /16 ip addresses(subnet filtering). I now see that the
src_ip_mask and dst_ip_mask is 32 bits and a separate
RTE_NTUPLE_FLAGS_SRC_IP
<http://dpdk.org/doc/api/rte__eth__ctrl_8h.html#aff1204ca0b33628610956f840dd9b206>
  has been introduced. Does this imply that we NOW support subnet
filtering(use mask for wildcard masking)?


Any help or pointers on the subject will be greatly appreciated!!!


Thanks,
Kam

             reply	other threads:[~2015-08-04 20:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-04 20:44 Kamraan Nasim [this message]
2015-08-04 21:40 ` Vladimir Medvedkin
2015-08-05 14:53   ` Kamraan Nasim
2015-08-05 15:18     ` Vladimir Medvedkin

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='CAPrTskjdDc1GPUUSCRjG1r+TjodXXd2+=2J7M6c=jV8+-kpRhA@mail.gmail.com' \
    --to=knasim@sidebandnetworks.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=helin.zhang@intel.com \
    --cc=jdu@sidebandnetworks.com \
    /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).