From owner-svn-src-head@freebsd.org Thu Jun 2 12:57:42 2016 Return-Path: Delivered-To: svn-src-head@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 940F6B64ACA; Thu, 2 Jun 2016 12:57:42 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5EE581A5D; Thu, 2 Jun 2016 12:57:42 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (unknown [62.141.129.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 793671FE024; Thu, 2 Jun 2016 14:57:40 +0200 (CEST) Subject: Re: svn commit: r301197 - head/sys/dev/xen/netfront To: =?UTF-8?Q?Roger_Pau_Monn=c3=a9?= References: <201606021114.u52BEQqB047172@repo.freebsd.org> <2c81e44d-65de-10f0-8837-f23896855150@selasky.org> <20160602125422.gmdsueoeu5fiiec5@mac> Cc: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org From: Hans Petter Selasky Message-ID: Date: Thu, 2 Jun 2016 15:01:03 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: <20160602125422.gmdsueoeu5fiiec5@mac> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.22 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: Thu, 02 Jun 2016 12:57:42 -0000 On 06/02/16 14:54, Roger Pau Monné wrote: > On Thu, Jun 02, 2016 at 01:19:56PM +0200, Hans Petter Selasky wrote: >> On 06/02/16 13:14, Roger Pau Monné wrote: >>> + callout_reset(&rxq->rx_refill, hz/10, xn_alloc_rx_buffers_callout, >>> + rxq); >> >> Maybe use callout_reset_curcpu() to take advantage of callout's SMP >> capabilities ? > > Yes, that's fine. But what's the benefit of it? I don't really care whether > the callout is run on the current CPU or not. Is callout_reset_curcpu > cheaper than callout_reset? > Hi, It is maybe not cheaper, but it will distribute the load of the xn_alloc_rx_buffers_callout() callback, to the current CPU calling callout_reset_curcpu(). Else xn_alloc_rx_buffers_callout() will always be called from callback thread zero. --HPS