From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt0-f181.google.com (mail-qt0-f181.google.com [209.85.216.181]) by dpdk.org (Postfix) with ESMTP id A08D31B582 for ; Sun, 5 Aug 2018 21:03:29 +0200 (CEST) Received: by mail-qt0-f181.google.com with SMTP id d4-v6so11522655qtn.13 for ; Sun, 05 Aug 2018 12:03:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=domainhart-com.20150623.gappssmtp.com; s=20150623; h=from:mime-version:subject:message-id:date:to; bh=XeUylH35+kpOoB93GDGZwEQHqAz/Ba9Rmf9OdtGpHYw=; b=JJTDa8rM5nYtxS38E30Lu4XkrhVDvq51UlEKHzU9jezOE1Wtm2QuvKjfs8PMuNC+lt qnzr6EOIeisP11XGGlgSbvEA7Sf03B0K0umxfOb5Vk/etTJx0IocrR8nYSZN0tFrxZ5H 0ZBiVPMv7PomSIZgtZ552HDf5Y54PCvhFTeroNtUizgwGTYwVbRzefGNdk5F2mGPFhIF ghr2uj8NNbZz4ph2l7N7zaKhRz7D0noYp+cIdZIIoYcUp5uijXVfKLCwJpgr4CcqcYGU zQHyn7YFc6uQePYUkk10gs5+ZD2W2cxe1w9F1Xi9AblWBs5SuQr8mgFojlzU3U5Nf5WD csZg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:message-id:date:to; bh=XeUylH35+kpOoB93GDGZwEQHqAz/Ba9Rmf9OdtGpHYw=; b=A9f7KuK54T1IUFdaKVZskTgyRvw2Sh1P4gYQj5Q160boaE+wH3OcTmw1THLhlkRgYi LCiCEYn8HjTHWSWFCtgOr+HxQvf79CjR53it89DHeEuyD5bqRTl07S1ODsREhaq1pyMT QVEOeJXVq1jKgPSsl2lGn1+lWpkMZzORFy4tJkJqJU8A6h0wUujQEUKep4a551Rbfa+s lcSdOp/9J/9lsa93vkMKJl9pZv0nnQXfI/9k+jBmVhHUT1AAZ9NqqPGZekvneklcfiw3 GJhNylOA8A9jEA1OfsZN3Ad7ZUDJm7NT+RdnH9QK2XiO3icC6LOvFbyMq5WhD2+rVEyw kC/g== X-Gm-Message-State: AOUpUlEa0hEGjeihWGjm+da04XEG1rsyV2wXiruz+Q+56GungBdFXCrW cpp4pWUiU+LSrnEkX6mOtXrvJUl4NgY= X-Google-Smtp-Source: AAOMgpfN6reLLbMtEhZWjT5HUDv4QeRE/sCmJdvaa+YqCW22kOP65ytmLI28h9IaXYpiK4WlrvtQ1A== X-Received: by 2002:a0c:bfd8:: with SMTP id u24-v6mr10643556qvj.158.1533495808681; Sun, 05 Aug 2018 12:03:28 -0700 (PDT) Received: from thart-mac.fios-router.home (pool-173-76-218-223.bstnma.fios.verizon.net. [173.76.218.223]) by smtp.gmail.com with ESMTPSA id m40-v6sm7597507qtb.63.2018.08.05.12.03.27 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 05 Aug 2018 12:03:27 -0700 (PDT) From: Anthony Hart Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Message-Id: <3338AA01-BB97-494F-B39C-6A510D085C79@domainhart.com> Date: Sun, 5 Aug 2018 15:03:26 -0400 To: users@dpdk.org X-Mailer: Apple Mail (2.3445.9.1) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-users] eventdev performance 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: Sun, 05 Aug 2018 19:03:29 -0000 I=E2=80=99ve been doing some performance measurements with the = eventdev_pipeline example application (to see how the eventdev library = performs - dpdk 18.05) and I=E2=80=99m looking for some help in = determining where the bottlenecks are in my testing. I have 1 Rx, 1 Tx, 1 Scheduler and N worker cores (1 sw_event0 device). = In this configuration performance tops out with 3 workers (6 cores = total) and adding more workers actually causes a reduction in = throughput. In my setup this is about 12Mpps. The same setup running = testpmd will reach >25Mpps using only 1 core. This is the eventdev command line. eventdev_pipeline -l 0,1-6 -w0000:02:00.0 --vdev event_sw0 -- -r2 -t4 = -e8 -w70 -s1 -n0 -c128 -W0 -D This is the tested command line. testpmd -w0000:02:00.0 -l 0,1 -- -i --nb-core 1 --numa --rxq 1 --txq 1 = --port-topology=3Dloop I=E2=80=99m guessing that its either the RX or Sched that=E2=80=99s the = bottleneck in my eventdev_pipeline setup. =20 So I first tried to use 2 cores for RX (-r6), performance went down. = It seems that configuring 2 RX cores still only sets up 1 h/w receive = ring and access to that one ring is alternated between the two cores? = So that doesn=E2=80=99t help. Next, I could use 2 scheduler cores, but how does that work, do they = again alternate? In any case throughput is reduced by 50% in that = test. thanks for any insights, tony