From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id AA56DC34E for ; Wed, 17 Feb 2016 18:23:40 +0100 (CET) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga102.fm.intel.com with ESMTP; 17 Feb 2016 09:23:39 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,461,1449561600"; d="scan'208";a="748125582" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.208.63]) by orsmga003.jf.intel.com with SMTP; 17 Feb 2016 09:23:37 -0800 Received: by (sSMTP sendmail emulation); Wed, 17 Feb 2016 17:23:37 +0025 Date: Wed, 17 Feb 2016 17:23:37 +0000 From: Bruce Richardson To: Paul Atkins Message-ID: <20160217172336.GC11736@bricha3-MOBL3> References: <1454084293-5722-1-git-send-email-patkins@brocade.com> <1600067.TyQ2MXbqf2@xps13> <56AB97BE.9030106@brocade.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <56AB97BE.9030106@brocade.com> Organization: Intel Shannon Ltd. User-Agent: Mutt/1.5.23 (2014-03-12) Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH 0/3] null driver improvements for testability X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Feb 2016 17:23:41 -0000 On Fri, Jan 29, 2016 at 04:47:58PM +0000, Paul Atkins wrote: > Hi Thomas, > > On 29/01/16 16:31, Thomas Monjalon wrote: > >Hi Paul, > > > >2016-01-29 16:18, Paul Atkins: > >>This patchset adds functionality to the null driver help when testing > >>a dataplane that uses dpdk. The idea is that the the dataplane can > >>have multiple null interfaces attached, and each of theses can be > >>assigned a mac address. Packets can then be injected into the null > >>drivers by adding them to a ring, giving the application complete > >>control of the packets that arrive. Packets that are sent by a null > >>driver can be stored on a ring, where the application can pick them up > >>and verify it is what was expected. To allow the application to know > >>when packets have been pulled of the rx ring, counters of the number of > >>times an rx poll has been made are kept, and these can be retrieved via > >>the existing APIs. > >I have not read your code, just read this description. > >It sounds like being a ring PMD. Have you already checked it? > >https://urldefense.proofpoint.com/v2/url?u=http-3A__dpdk.org_browse_dpdk_tree_drivers_net_ring_rte-5Feth-5Fring.c&d=CwICAg&c=IL_XqQWOjubgfqINi2jTzg&r=45ezphVDEm8OnEpH-fLWdXvR3RneLhhNZRDLQRgR6LY&m=wJLO24XFe_B0nZve6mkvocCt7fQWo3PULCTWxrC8rZk&s=bIWycJrY-PYgzkQsBeRfkl8JCHFcxRAHhHDrqRSzHYs&e= > > I hadn't seen the ring PMD. I will have a look at it and see if I can make > it do what i need. > > thanks, > Paul Hi Paul, any update on this. Your patches are still showing as pending in patchwork, but if ring pmd is more what need, we can set these patches aside as unneeded, and remove them from the patchwork merge backlog. thanks, /Bruce