From owner-freebsd-current@freebsd.org  Thu Jan 12 00:54:52 2017
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id ED849CA987A;
 Thu, 12 Jan 2017 00:54:52 +0000 (UTC)
 (envelope-from mmacy@nextbsd.org)
Received: from sender163-mail.zoho.com (sender163-mail.zoho.com
 [74.201.84.163])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id D7C06131D;
 Thu, 12 Jan 2017 00:54:52 +0000 (UTC)
 (envelope-from mmacy@nextbsd.org)
Received: from mail.zoho.com by mx.zohomail.com
 with SMTP id 1484182483952176.91086989048313;
 Wed, 11 Jan 2017 16:54:43 -0800 (PST)
Date: Wed, 11 Jan 2017 16:54:43 -0800
From: Matthew Macy <mmacy@nextbsd.org>
To: =?UTF-8?Q?=22Olivier_Cochard-Labb=C3=A9=22?= <olivier@freebsd.org>
Cc: "Sean Bruno" <sbruno@freebsd.org>, 
 "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>, 
 "freebsd-current@freebsd.org" <freebsd-current@freebsd.org>
Message-ID: <159902b73ed.10775291e21533.7488368455500235608@nextbsd.org>
In-Reply-To: <CA+q+Tcp5LwrnXt75tNpYpAr1KWx9YpLx5kMHhPR+YgAs__n1eA@mail.gmail.com>
References: <30f21c75-d3a2-edcd-1999-d5ed9f970c06@freebsd.org>
 <b000a957-8d17-a04d-6275-0d3920aa8a17@freebsd.org>
 <CA+q+TcramTrYgYT-s+=aBZzRJV8FmKQqGt=1twPhLBR7AoXkcQ@mail.gmail.com>
 <1598d97bf2a.c6bcb76838987.6501340920645175463@nextbsd.org>
 <574a7ac7-4842-9518-8286-a4d89a9f7a27@freebsd.org>
 <CA+q+Tco-dcoU8EZnDEzgoK-v2Q2=U5GF6ASMSj0kwzd_wB5xig@mail.gmail.com>
 <6c6cb534-73c7-464b-8af1-7445a9c0188c@freebsd.org>
 <1598f29d379.ea6360351471.8752933472741761813@nextbsd.org>
 <CA+q+TcpUXXPEQtdMFup6EZzyCKs9Ep+nS5SB+fm6bSJSDs34_w@mail.gmail.com>
 <1598f3f8588.d20017893749.339651164872952258@nextbsd.org>
 <1598f42ad77.eeec05be4113.9201780237587761460@nextbsd.org>
 <CA+q+Tcp5LwrnXt75tNpYpAr1KWx9YpLx5kMHhPR+YgAs__n1eA@mail.gmail.com>
Subject: Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb
 pending
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Priority: Medium
User-Agent: Zoho Mail
X-Mailer: Zoho Mail
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jan 2017 00:54:53 -0000

 >  A flame graph for the core cycle count and a flame graph with cache mis=
s stats from pmc would be a great start.
 > =20
 >=20
 > =E2=80=8BI didn't know the exact event name to use for cache miss stats,=
 but here are the flame graphs for CPU_CLK_UNHALTED_CORE:
 > http://dev.bsdrp.net/netgate.r311848.CPU_CLK_UNHALTED_CORE.svg
 > http://dev.bsdrp.net/netgate.r311849.CPU_CLK_UNHALTED_CORE.svg

Thanks. Having twice as many txqs would definitely help. It's also clear th=
at there may be some sort of peformance issue in iflib_txq_drain. Although =
it could just be non-stop cache misses on the packet headers.

-M