From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <knasim@sidebandnetworks.com>
Received: from mail-ob0-f181.google.com (mail-ob0-f181.google.com
 [209.85.214.181]) by dpdk.org (Postfix) with ESMTP id D54F05686
 for <dev@dpdk.org>; Wed, 14 Jan 2015 22:59:17 +0100 (CET)
Received: by mail-ob0-f181.google.com with SMTP id gq1so10447062obb.12
 for <dev@dpdk.org>; Wed, 14 Jan 2015 13:59:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=sidebandnetworks.com; s=google;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=glOqpf+Cz+4Z5IhmK1ZIPNJxB7TdHDp0E925rfAZsrE=;
 b=NOKp+C8009wnMRiwBtx7iJG0+rQf0RRsQGU5DwIy8xh/pT17jvQLEX4yblrJcYPsHL
 HTohIw4fCRzqUpPrtpUHzSi3aFf/4yRqGjVV40Ys9OhmgzdHW3Xtc4X4tYD31OOhqoLr
 pcPkeYSB03jA0weMYWDmZjF9pEQByMF0BETHY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:in-reply-to:references:date
 :message-id:subject:from:to:cc:content-type;
 bh=glOqpf+Cz+4Z5IhmK1ZIPNJxB7TdHDp0E925rfAZsrE=;
 b=az/85nt+hfqkaVe1lBaE/wGXKPeMr7qdSse3FqxUAEupwynRdcG811dDIj8mb9LDHl
 zakC6gdL5pz1D4Obk0b9C0TfJl+iB2H6zwLY+q7OnWIiz9Wdhl5/7oVww/H+Ipux9eit
 tKZEqZjtUl49TlQm6sVXJKKlKtvCWInuDyJYyY7EwOJe0Ulh/M0VlJVgE7eEkTUuStdS
 sXI7Mb9BrB/QMaSyl9rTekh582piMFVBCcEwUWAwYhU09+TuJ7y/yjLi8phMIrIkbFhV
 fgb9WlS5I935NubcbvWEbAwJY/KJ/RK3odptBBfdXLSne1j33C/XcFwGzTfC2OJ+GGn0
 m/mQ==
X-Gm-Message-State: ALoCoQk29KG/nXAWCLAKL9z/iF7Ej9cEI6UPFRIrFnKQn4W6kkKcKBRRF+Ln9fi8KOoIQSvJisf0
MIME-Version: 1.0
X-Received: by 10.202.53.139 with SMTP id c133mr3572134oia.109.1421272757171; 
 Wed, 14 Jan 2015 13:59:17 -0800 (PST)
Received: by 10.202.48.79 with HTTP; Wed, 14 Jan 2015 13:59:17 -0800 (PST)
In-Reply-To: <20150114102722.GC10476@bricha3-MOBL3>
References: <CAPrTskjo7U_eGpprgLyJ0WDYy6eSttwRswobUP3mxNpsfLy0qw@mail.gmail.com>
 <20150114102722.GC10476@bricha3-MOBL3>
Date: Wed, 14 Jan 2015 16:59:17 -0500
Message-ID: <CAPrTskhLO+zvYtc=t=O5bm90+b1E7DGZ+q6XgyRxWR1cTegcvQ@mail.gmail.com>
From: Kamraan Nasim <knasim@sidebandnetworks.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Cc: dev@dpdk.org, Ean Houts <ehouts@sidebandnetworks.com>,
 Jun Du <jdu@sidebandnetworks.com>
Subject: Re: [dpdk-dev] Does I210 NIC support Flow director filters?
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: Wed, 14 Jan 2015 21:59:18 -0000

Many thanks Helin and Bruce :)

Now if 1Gb NICs don't support fdir filters then im wondering how would we
count the number of packets matching a filter.

Regular 5tuple filters don't have any stats similar to "fdirmatch"(in the
rte_eth_stats <http://dpdk.org/doc/api/structrte__eth__stats.html> struct).
One way I can think of is to use regular ibytes/ipackets stats for the
queue to which the packets are being redirected in the 5tuple filter but
this seems a bit hacky + there is no way to distinguish this packet
throughput from the regular traffic that the NIC is forwarding to that
specific queue.

Is there a way to EXCLUSIVELY bind a 5tuple filter to an RSS queue so that
only matched traffic is forwarded there?


--Kam

On Wed, Jan 14, 2015 at 5:27 AM, Bruce Richardson <
bruce.richardson@intel.com> wrote:

> On Tue, Jan 13, 2015 at 11:21:08PM -0500, Kamraan Nasim wrote:
> > Hello,
> >
> > I've been using DPDK fdir filter APIs for 82599 NIC(Niantic) and they
> work
> > very well.
> >
> > Was wondering if I these could also be used for I210, 1Gbps NICs?
> >
> > The other option is to use 5tuple filters(rte_eth_dev_add_5tuple_filter
> > <
> http://dpdk.org/doc/api/rte__ethdev_8h.html#aaa28adafa65a4f47d4aeceaf1b08381b
> >),
> > however these do not support IPv6 yet.
> >
> >
> > Have people in the community had any luck with configuring L3/L4 hardware
> > filters for the I210 NIC?
> >
> > Thanks,
> > Kam
>
> Flow director filters are not supported for 1G NICs. Sorry.
>
> /Bruce
>