From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.228.170]) by dpdk.org (Postfix) with ESMTP id B5212137C for ; Tue, 27 Sep 2016 21:29:16 +0200 (CEST) Received: by mail.mhcomputing.net (Postfix, from userid 1000) id 412DF94D; Tue, 27 Sep 2016 12:29:16 -0700 (PDT) Date: Tue, 27 Sep 2016 12:29:16 -0700 From: Matthew Hall To: Cody Doucette Cc: users@dpdk.org Message-ID: <20160927192916.GA1997@mhcomputing.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [dpdk-users] filtering IPv6 packets in hardware X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Sep 2016 19:29:17 -0000 On Tue, Sep 27, 2016 at 12:06:25PM -0400, Cody Doucette wrote: > Has anyone encountered this problem before? Any tips on how I could make > this work -- or even suggestions for better hardware? In general these problems are very commonplace among the community members. We have had many painful discussions on these topics since you only get 9.6 nanoseconds and only so many opcodes to handle each new frame. >>From the software side the distributor framework could help. >>From the hardware side you have to read all of the data sheets for the chips supported by each PMD to find the chip with the right features for your use case. > Thanks! > Cody Matthew.