From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 392F2A00E6 for ; Mon, 10 Jun 2019 16:40:17 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id A828D1C07B; Mon, 10 Jun 2019 16:40:16 +0200 (CEST) Received: from smtp-out.abv.bg (smtp-out.abv.bg [194.153.145.80]) by dpdk.org (Postfix) with ESMTP id BDBF11C068 for ; Mon, 10 Jun 2019 16:40:14 +0200 (CEST) Received: from nm22.abv.bg (mail92.ni.bg [192.168.151.143]) by smtp-out.abv.bg (Postfix) with ESMTP id 53F2C4A7AD for ; Mon, 10 Jun 2019 17:40:14 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=abv.bg; s=smtp-out; t=1560177614; bh=VA25vjRvJ4pRh7jf8vYkFi89HgfZZQsdcsjBc40PSpk=; h=Date:From:To:Subject:From; b=LQMO+/HLInnAK4WIBhpsWY4RRVCzEVd/FvcSPeN6RVck++UDRogiF9CeaL8rQlBwe VT351GCci72eerQ1XG55sGkgWL7XBKLZBZWcfIjuhV7WjhC69Ln9QIJBB5u7Y87bqs jNE2sTSN1SCZ9tx+bRyVm6I0DxkcTyTUI9D1kTo4= Received: from nm22.abv.bg (localhost [127.0.0.1]) by nm22.abv.bg (Postfix) with ESMTP id 5057E9D801 for ; Mon, 10 Jun 2019 17:40:14 +0300 (EEST) Date: Mon, 10 Jun 2019 17:40:14 +0300 (EEST) From: George Yaneff To: users@dpdk.org Message-ID: <1567292027.2330305.1560177614329@nm22.abv.bg> MIME-Version: 1.0 X-Mailer: AbvMail 3.0 X-Originating-IP: 78.83.11.106 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-users] DPDK Distributor app issues X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Sender: "users" I'm playing with the distributor example application from dpdk 19.05.0 I have three machines connected sequentially with an UTP Ethernet cable. The middle is Ubuntu 18.04.2 LTS with a eigth core Intel I7 processor and 24 GB ram. The eth device used is Intel I350 with four ports. The strange behavior I'm observing is when I ping the second node from the first node (traffic passing through the distributor) there are always one or two packets lost. When I use l2fwd or basicfwd applications there is no packet loss. Anyone knows if this is normal or if it is not - what I'm doing wrong? Another thing I noticed is that the ping replies come to the first node with around one second of delay. (1024ms on most packets) Again there is no latency with the basicfwd (packets arriving in 0.101 ms there). Is there any way to minimize this delay in distributor application also? George