From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <knasim@sidebandnetworks.com>
Received: from mail-oi0-f41.google.com (mail-oi0-f41.google.com
 [209.85.218.41]) by dpdk.org (Postfix) with ESMTP id 7D07F5ABA
 for <dev@dpdk.org>; Tue,  4 Aug 2015 22:44:17 +0200 (CEST)
Received: by oip136 with SMTP id 136so9550532oip.1
 for <dev@dpdk.org>; Tue, 04 Aug 2015 13:44:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=sidebandnetworks.com; s=google;
 h=mime-version:date:message-id:subject:from:to:cc:content-type;
 bh=omE3a3qFubPMspvZtVN6ygOiWEyMGdFh+Exe5sZElBc=;
 b=M36O3bzheWbLZE26/1NLMQzP4U15dd9yubVE1yxUiU8myQzR5Rjjg8Tq6PYlg2rtAl
 JpdXxWHMQra7MsvHjsmfwTYvXsV3mJUL4jNhavNP7TK2Xtlji5iiVzEE/uR5CJPsW949
 1uvjIDoOHA7FZXfJ/C/06mJ+sBOidOtmbf/2Q=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:date:message-id:subject:from:to:cc
 :content-type;
 bh=omE3a3qFubPMspvZtVN6ygOiWEyMGdFh+Exe5sZElBc=;
 b=iX93Y9UGs6OLfkjvl3JmPrdsu33leU+C0DHujw+j6VXhoyyHmnkFryp8XnNLNAwaIS
 c/M20lLuq3rksTmNMPZoMpuJg/K07aidGAG4XMleiEggBHMq445kVSyNlFzmmD2MKxL6
 bpNXrJXgu1vt7cyMETjusxhCQRFHpy8uambPAWRLhmcWWxGG7zG2xNlEoEy9bZTGQIzy
 eL+UnsHPs1TkcF+lj4EmhiHt1tJdIdbv7gxhpEWM7zh9rIqTkaIfOFp2gDpXe5hDaUK0
 SePDt8B+xVxxo6QlSIuRJ1zGhLGw/5V0WhkVcFG0illRzexTyUPKi860ky1wq9znHgOF
 9ylQ==
X-Gm-Message-State: ALoCoQk4uFTf5X2vmVw8cFOkuPoQ3FgimG9HAYxd+09tw1jbIgTdfFIkNPtrRSQxPqKCSlDdn1+t
MIME-Version: 1.0
X-Received: by 10.202.60.87 with SMTP id j84mr4796834oia.48.1438721056973;
 Tue, 04 Aug 2015 13:44:16 -0700 (PDT)
Received: by 10.202.226.146 with HTTP; Tue, 4 Aug 2015 13:44:16 -0700 (PDT)
Date: Tue, 4 Aug 2015 16:44:16 -0400
Message-ID: <CAPrTskjdDc1GPUUSCRjG1r+TjodXXd2+=2J7M6c=jV8+-kpRhA@mail.gmail.com>
From: Kamraan Nasim <knasim@sidebandnetworks.com>
To: dev@dpdk.org, "Zhang, Helin" <helin.zhang@intel.com>, 
 Bruce Richardson <bruce.richardson@intel.com>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Cc: Jun Du <jdu@sidebandnetworks.com>
Subject: [dpdk-dev] Changes to 5tuple IPv4 filters in dpdk v2.0
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Aug 2015 20:44:17 -0000

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