From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f170.google.com (mail-wr0-f170.google.com [209.85.128.170]) by dpdk.org (Postfix) with ESMTP id 25D041C734 for ; Wed, 4 Apr 2018 17:00:26 +0200 (CEST) Received: by mail-wr0-f170.google.com with SMTP id m13so23222959wrj.5 for ; Wed, 04 Apr 2018 08:00:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telco.com; s=google; h=message-id:subject:from:to:date:mime-version :content-transfer-encoding; bh=qB7sEZfZSu/47FwTSEdls1WZPA/HxtbJF3FmC2pWcBI=; b=hT5NQe5xgNuj1XUTLiG9NOrGblykhXw5SP3CkMwg1seUVym2tDv7NNjhZp1nnpX0TD 8bTcir5Yd16MG2UIMH6r9p0ThlSokg0Y6W2NjbqsiVd8j67BYxfn7tumMWGMXVCdEjEd GmvTzZpLh/lD8qkdWMgX/8oSbLEr3OIafu/CM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:mime-version :content-transfer-encoding; bh=qB7sEZfZSu/47FwTSEdls1WZPA/HxtbJF3FmC2pWcBI=; b=Yxof7gd6smVXfrMX86iQnaihf60UTxUjzN+J6LQEK9n6MA5PYIxBpdcgBZSOojq7+P cmQlvy/L3gMSAOeS6NJBZu7oUSQ6D3IdKHhFFf6jc4pLyMo3+vwx44dC2QQLx2xtSOqT GSZxhvRJuS/Kntb0EiTa3Ac6Z372nKSDMBAK81d001cwaxZVT1w6GHxjGlgZkJVfc/rT EGXxDsZn614PtAOno6V+zKEQiBjRg9m1VEdfgtO2pIlGS6x2l1izvzaW2DAupOhlz0FH UcB7/YFNCPA0u+PB9UrNEBBVGmgovDzAukflMUPQe5IdoM/xoSQAkhbA0xmESuZzGs48 ZSLw== X-Gm-Message-State: ALQs6tBZA3LVyq7XlaMWXvJ6thnkKtR5oculGhZ19v+zQW66Vpnbclsb yuG6uPlaXIaEK0a3kSkmuyGBJMN27+o= X-Google-Smtp-Source: AIpwx49j4E6rJjKpl9fsda43UF43v9DVrolu0xG0bTTT9ZvszVXr2RXmBKzWFmIMJYpeeX2NU/UV0Q== X-Received: by 2002:a19:a003:: with SMTP id j3-v6mr10938726lfe.8.1522854025667; Wed, 04 Apr 2018 08:00:25 -0700 (PDT) Received: from localhost.localdomain ([80.239.223.196]) by smtp.gmail.com with ESMTPSA id d81-v6sm1049307lfd.49.2018.04.04.08.00.24 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 04 Apr 2018 08:00:24 -0700 (PDT) Message-ID: <1522854024.2705.17.camel@telco.com> From: Dawid Deja To: users@dpdk.org Date: Wed, 04 Apr 2018 17:00:24 +0200 Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.26.1 (3.26.1-1.fc27) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [dpdk-users] OVS-DPDK performance raises when stress is running on the same core 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, 04 Apr 2018 15:00:26 -0000 Hello, I was testing how the OVS-DPDK will perform when putted into cgroup. To my surprise, the performance raises once ovs-vswitchd process was able to consume only 50% of CPU. Here's what I've done: 1. I have configured OVS to use dpdk and to run on core no 2; 2. I have created bridge with datapath_type=netdev, added a dpdk interface to it and connected a VM to this bridge via vhostuser port; 3. I have created new cgroup, set the cpu.shares to 512 and added the pid of ovs-vswitchd process to tasks; At that point, I measured the throuhput from the VM, via the dpdk interface to the external machine using iperf3: iperf3 -c 192.168.0.3 -M 104 The bandwith was around 40Mb/s. After that: 4. I have started stress process to stress one core (# stress -c 1); 5. I have added the stress process to cgroup created in point 3; 6. Using taskset, I've put stress on same core as ovs-vswitchd; Then I run the iperf3 again, with same command. The bandwith was around 100 Mb/s.Can this be explained somehow? The tests were run on host with Atom CPU (Intel(R) Atom(TM) CPU C2758 @ 2.40GHz). Thanks, Dawid Deja