From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <bruce.richardson@intel.com>
Received: from mga02.intel.com (mga02.intel.com [134.134.136.20])
 by dpdk.org (Postfix) with ESMTP id 44D4258F1
 for <dev@dpdk.org>; Fri, 16 Jan 2015 18:32:03 +0100 (CET)
Received: from orsmga002.jf.intel.com ([10.7.209.21])
 by orsmga101.jf.intel.com with ESMTP; 16 Jan 2015 09:32:02 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.09,412,1418112000"; d="scan'208";a="671159467"
Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.220.24])
 by orsmga002.jf.intel.com with SMTP; 16 Jan 2015 09:31:59 -0800
Received: by  (sSMTP sendmail emulation); Fri, 16 Jan 2015 17:31:59 +0025
Date: Fri, 16 Jan 2015 17:31:59 +0000
From: Bruce Richardson <bruce.richardson@intel.com>
To: Kamraan Nasim <knasim@sidebandnetworks.com>
Message-ID: <20150116173158.GA9528@bricha3-MOBL3>
References: <CAPrTskjo7U_eGpprgLyJ0WDYy6eSttwRswobUP3mxNpsfLy0qw@mail.gmail.com>
 <20150114102722.GC10476@bricha3-MOBL3>
 <CAPrTskhLO+zvYtc=t=O5bm90+b1E7DGZ+q6XgyRxWR1cTegcvQ@mail.gmail.com>
 <20150115144449.GA1880@bricha3-MOBL3>
 <CAPrTskg+VOrW3K1i4AzT=kZOm+KxnDiusVH3WWq5sg+r0UKJag@mail.gmail.com>
 <20150116105627.GB10516@bricha3-MOBL3>
 <CAPrTskgx8NOdxKKVjNiw50wumcN8gMxE2k_6+4ofGV8BdPbiDQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAPrTskgx8NOdxKKVjNiw50wumcN8gMxE2k_6+4ofGV8BdPbiDQ@mail.gmail.com>
Organization: Intel Shannon Ltd.
User-Agent: Mutt/1.5.23 (2014-03-12)
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: Fri, 16 Jan 2015 17:32:03 -0000

On Fri, Jan 16, 2015 at 11:42:42AM -0500, Kamraan Nasim wrote:
> Hi Bruce,
> Perhaps this can be worked around by setting  rx_drop_en in the
> rte_eth_rxconf <http://dpdk.org/doc/api/structrte__eth__rxconf.html> and
> using small values for number of rx descripters so that the NIC drops when
> it is out of RX descriptors for that queue?
> 
> As long as NIC can still provide q_ipackets/q_errors then this might be
> faster than doing a RX in software and drop.
> 
> --Kam

Yes, so long as packets dropped for that queue are counted against that queue,
then yes.

/Bruce

> 
> On Fri, Jan 16, 2015 at 5:56 AM, Bruce Richardson <
> bruce.richardson@intel.com> wrote:
> 
> > On Thu, Jan 15, 2015 at 08:06:52PM -0500, Kamraan Nasim wrote:
> > > >>> update the RSS RETA table so that traffic doesn't get sent
> > > >> to that queue via RSS. Is that what you are asking?
> > >
> > > Thanks Bruce, that's exactly it.  Basically each filter will forward
> > > traffic to a unique RSS queue which can allow me to calculate filter
> > match
> > > statistics for that queue(or filter). At that point I would like to drop
> > > the filtered packet. Is there any way to drop the filtered packet in the
> > > RSS queue without doing a rte_eth_rx_burst() and dropping it then?
> > >
> > > --Kam
> > >
> > I don't believe there is any other way to drop them from the queue other
> > than
> > RX and drop. It's not the most efficient way to do so (since you have to
> > allocate,
> > fill and free an mbuf), but it's the only way that an app can do so without
> > adding new functions to the driver(s).
> >
> > /Bruce
> >