From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mgw.gov.kz (mgw.gov.kz [89.218.88.242]) by dpdk.org (Postfix) with ESMTP id 89A5BADB6 for ; Wed, 15 Jun 2016 12:04:00 +0200 (CEST) Received: from sts.kz (mail.sts.kz [178.89.4.9]) by mgw.gov.kz with ESMTP id u5FA3x0Q012787-u5FA3x0S012787 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 15 Jun 2016 16:03:59 +0600 Received: from [172.20.19.232] (unknown [178.89.4.11]) by sts.kz (Postfix) with ESMTPA id 42A45652A; Wed, 15 Jun 2016 16:03:59 +0600 (ALMT) DKIM-Filter: OpenDKIM Filter v2.10.3 sts.kz 42A45652A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sts.kz; s=mail; t=1465985039; bh=ZcEIJR5Ni0HfPurCEvgUl0vrcDGxyP0mmHO0Dk+h0uk=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=4VLuOKx4ksFdtQtXNnXDwBc6BstYteLK2JhjkRXb0SjdHgGFF9u+pEqkJMP3/wK0t FXBBAFqe8W0dWFFVEmiKAr3lpGc9bb0Em7xDec4NGdGE1Giesl/pUSrP3xWggSZlfv YXJ1qnqXr7to0rXVHrzLGsPKIKQWi8vTnZrZty9g= To: Bruce Richardson References: <5761235C.2090906@sts.kz> <20160615094922.GB10172@bricha3-MOBL3> Cc: dev@dpdk.org From: Yerden Zhumabekov Message-ID: <5761280F.6020106@sts.kz> Date: Wed, 15 Jun 2016 16:03:59 +0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 MIME-Version: 1.0 In-Reply-To: <20160615094922.GB10172@bricha3-MOBL3> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] random pkt generator PMD 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, 15 Jun 2016 10:04:00 -0000 On 15.06.2016 15:49, Bruce Richardson wrote: > On Wed, Jun 15, 2016 at 03:43:56PM +0600, Yerden Zhumabekov wrote: >> Hello everybody, >> >> DPDK already got a number of PMDs for various eth devices, it even has PMD >> emulations for backends such as pcap, sw rings etc. >> >> I've been thinking about the idea of having PMD which would generate mbufs >> on the fly in some randomized fashion. This would serve goals like, for >> example: >> >> 1) running tests for applications with network processing capabilities >> without additional software packet generators; >> 2) making performance measurements with no hw inteference; >> 3) ability to run without root privileges, --no-pci, --no-huge, for CI >> build, so on. >> >> Maybe there's no such need, and these goals may be achieved by other means >> and this idea is flawed? Any thoughts? > Isn't some of this already covered by the NULL PMD? Perhaps it could be extended > or enhanced to meet some more of your requirements? > > /Bruce Right, but development of various features regarding L3/L4 etc requires more subtle approach, like live packets, different protocol versions, fields manipulation. In this case some packet mangling/randomizing capabilities would be quite useful. Something similar to what is done in Pktgen, but more lightweight approach, in a same app. I've almost made my mind :) so the next question: is there any guide on PMD dev? I'm looking through rte_ether.h right now, but some doc would be very nice.