From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg0-f47.google.com (mail-pg0-f47.google.com [74.125.83.47]) by dpdk.org (Postfix) with ESMTP id D6BB6FABA for ; Wed, 18 Jan 2017 17:55:43 +0100 (CET) Received: by mail-pg0-f47.google.com with SMTP id 204so5958868pge.0 for ; Wed, 18 Jan 2017 08:55:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=75AnL8kM9lJJadioyfIs2HoN1Fn8KtTCHR4u2gdk1eA=; b=Kjen2JDWuK94bYkbOCRI/sF3SjaalsclCvWg9oEqDZt/7VydgL36gZujo/ORvlbS2s 69kJxVzLR5e646fIJX7Gs1GBV7kvBKo8FoASiJs7ISC0CVd47tBTNPdb9j7Pn0Rn+ZIW RxExfTKOX8gGALFJ9pdyzF31IpV0xG/3fSXKwhvmiFBWrZxjWiwUwyVQ+Zpxab0NqSbJ f5sj+PD7GvjzVGJqJYGdQVpbO3CHnM4RB152dh60HdN2M5LdsryVJe1EPmrwuqi3MC7j aHCq3AKuiWBeQA7jibmDY7uUGLchNaHhxKgXZwkD8ZXNXbg2TcvnjqAYdoj11ThkkL8i pz3g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=75AnL8kM9lJJadioyfIs2HoN1Fn8KtTCHR4u2gdk1eA=; b=Ybb7oU1evwgqPw+JqcrPmdKNdRMj9LpUwf5gOAiyCKO52G48fNOS6fOFFoGyPxOkyA qMTIYWeyDnUq06TJ1UgWdbcwXiRv0usGG5Uk0v+0v7s0jxpCUkmJ93cHzKDtj+kZLtAs c1iNOOJUOQSJls8so3Ip119HT/3Sb4NXS4kWI+1jD+/Bif+NaiVlR/WIFWYlNhsj3D/U /Gr8SAcHHC2dtKi/usqDnFwPfPoHgL87KqIVGiL3EAuKz/kIdWTJXkmUOm3oB/tKFmYr R60N0AwBsKt5jwgLo0Pfn6G6R84BjIez7p++o/8zAHaVBIiKBi9mZ6cNyiP9dAJXO55+ ESZQ== X-Gm-Message-State: AIkVDXLzT2SJ6EdygdCGGhA9nqc8bZvdhtrr55Kbijj/6OHpWUdy1n+WrOrRr4ruZHpzpg== X-Received: by 10.99.145.68 with SMTP id l65mr5098298pge.12.1484758543052; Wed, 18 Jan 2017 08:55:43 -0800 (PST) Received: from xeon-e3 (204-195-18-65.wavecable.com. [204.195.18.65]) by smtp.gmail.com with ESMTPSA id g28sm2131597pgn.3.2017.01.18.08.55.42 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 18 Jan 2017 08:55:42 -0800 (PST) Date: Wed, 18 Jan 2017 08:55:35 -0800 From: Stephen Hemminger To: Marco Kwok Cc: users@dpdk.org Message-ID: <20170118085535.4bcfd124@xeon-e3> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-users] what is the average latency you get for io forwarding from dpdk? 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: , X-List-Received-Date: Wed, 18 Jan 2017 16:55:44 -0000 On Tue, 17 Jan 2017 16:28:01 +0800 Marco Kwok wrote: > My test platform is on a intel NUC NUC5I5RYH, which has i5 5250U 1.6GHz, > 16GB DDR3 and i218-V network chip. dpdk 16.07.2 You may need a faster cpu, and PCI gen3 support (so that NIC goes direct to CPU cache). Also i218-V uses E1000 driver which has not been optimized much. > I have done the following things try to get a better latency with no luck: > -setup 1G hugepages > -disable cpu frequency scaling to make sure cpu runs at max speed of 2.7GHz > -isolate a cpu core from kernel task scheduler by isolcpus > -setting the burst size of testpmd to 1 Disable hyper-threading Set burst size to 32, some drivers optimize for this. Use different prefetch values