From owner-svn-src-head@freebsd.org Mon Jan 27 20:23:05 2020 Return-Path: Delivered-To: svn-src-head@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2E29422D278; Mon, 27 Jan 2020 20:23:05 +0000 (UTC) (envelope-from glebius@freebsd.org) Received: from cell.glebi.us (glebi.us [162.251.186.162]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "cell.glebi.us", Issuer "cell.glebi.us" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4861Qc6XHxz47tZ; Mon, 27 Jan 2020 20:23:04 +0000 (UTC) (envelope-from glebius@freebsd.org) Received: from cell.glebi.us (localhost [127.0.0.1]) by cell.glebi.us (8.15.2/8.15.2) with ESMTPS id 00RKMxca037245 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 27 Jan 2020 12:22:59 -0800 (PST) (envelope-from glebius@freebsd.org) Received: (from glebius@localhost) by cell.glebi.us (8.15.2/8.15.2/Submit) id 00RKMxnZ037244; Mon, 27 Jan 2020 12:22:59 -0800 (PST) (envelope-from glebius@freebsd.org) X-Authentication-Warning: cell.glebi.us: glebius set sender to glebius@freebsd.org using -f Date: Mon, 27 Jan 2020 12:22:59 -0800 From: Gleb Smirnoff To: Cy Schubert Cc: Hans Petter Selasky , src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r357004 - in head/sys: kern sys Message-ID: <20200127202259.GW1268@FreeBSD.org> References: <202001230124.00N1OlXi029506@repo.freebsd.org> <23f272a4-c997-a454-19d6-10392713e71f@selasky.org> <20200124170532.GO1268@FreeBSD.org> <7d7db96d-26b1-1d2b-9f8d-a3f8fbe8c33c@selasky.org> <202001242023.00OKNXlS094989@slippy.cwsent.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <202001242023.00OKNXlS094989@slippy.cwsent.com> User-Agent: Mutt/1.12.2 (2019-09-21) X-Rspamd-Queue-Id: 4861Qc6XHxz47tZ X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-1.53 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-0.71)[-0.713,0]; NEURAL_HAM_LONG(-0.82)[-0.821,0]; ASN(0.00)[asn:27348, ipnet:162.251.186.0/24, country:US] X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jan 2020 20:23:05 -0000 On Fri, Jan 24, 2020 at 12:23:33PM -0800, Cy Schubert wrote: C> > Let not the network epoch become the new Giant of EPOCH's. There might C> > be realtime constraints for EPOCH's aswell. C> C> I also had that concern yesterday. C> C> Obtaining an EPOCH higher up the call stack or lower down depends on the C> workload. Are there any measurements that moving the EPOCHs higher in the C> call stack improves one workload (and configuration) or another? Could one C> type of workload or configuration benefit from this at the expense of C> another workload or configuration? Can you imagine a workload where calling epoch_enter/exit more often but for a shorter period of execution would be beneficial that calling it once for a packet? -- Gleb Smirnoff