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 2D990C486 for ; Wed, 15 Jun 2016 11:43:57 +0200 (CEST) Received: from sts.kz (mail.sts.kz [178.89.4.9]) by mgw.gov.kz with ESMTP id u5F9huAA008775-u5F9huAC008775 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 15 Jun 2016 15:43:56 +0600 Received: from [172.20.19.232] (unknown [178.89.4.11]) by sts.kz (Postfix) with ESMTPA id 288FC64CA for ; Wed, 15 Jun 2016 15:43:56 +0600 (ALMT) DKIM-Filter: OpenDKIM Filter v2.10.3 sts.kz 288FC64CA DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sts.kz; s=mail; t=1465983836; bh=mq867IGe4n4V825Uo19MhT+N4tMOf/3MGLUTFmFbzU4=; h=To:From:Subject:Date:From; b=2SdmvFgCaMQZ4Nr1yqV6oL8avt1Cj3CuT7FYJaeMq+wbfG4FMTPmFRSwBJsygJ5IU Zem+zHA8g8CC44JJ0TQbSBzLHCMNXDn7AL1kXmfMdgjMhKJ6C8uwqphGF7K+SMcAaE Fc+8UH6Cq0YAZkZtMGU2Q2N1FdPKCgQhXsoE8PjU= To: dev@dpdk.org From: Yerden Zhumabekov Message-ID: <5761235C.2090906@sts.kz> Date: Wed, 15 Jun 2016 15:43:56 +0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: [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 09:43:57 -0000 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?