From owner-freebsd-stable@FreeBSD.ORG Mon Feb 13 15:38:18 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4B641065670 for ; Mon, 13 Feb 2012 15:38:18 +0000 (UTC) (envelope-from c.kworr@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 698AC8FC24 for ; Mon, 13 Feb 2012 15:38:18 +0000 (UTC) Received: by bkcjg1 with SMTP id jg1so4599151bkc.13 for ; Mon, 13 Feb 2012 07:38:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=ghv1n34ESHjcuY81/rVtsNRQDUBwgCeqDWMqJBQZqPo=; b=TwDJ6uUtceKgX4OrURRmcACixF3Y/B41tyVx/mAyi6hb61QFRpwcyB6klA7fpUNX01 CGlnHHpB2JHi/VCVS8zB2WYgCjOCjHV2slwokjjR9/fGHksJe8bcPnLMo9pDpC6RekJO tiAF+bBzSEjDAA5lMJikjQd+f+EOo7/A01W/I= Received: by 10.204.136.197 with SMTP id s5mr7495254bkt.9.1329147497341; Mon, 13 Feb 2012 07:38:17 -0800 (PST) Received: from green.tandem.local (43-24-132-95.pool.ukrtel.net. [95.132.24.43]) by mx.google.com with ESMTPS id cz3sm47375854bkb.3.2012.02.13.07.38.15 (version=SSLv3 cipher=OTHER); Mon, 13 Feb 2012 07:38:16 -0800 (PST) Message-ID: <4F392E66.5070403@gmail.com> Date: Mon, 13 Feb 2012 17:38:14 +0200 From: Volodymyr Kostyrko User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0.1) Gecko/20120213 Firefox/10.0.1 SeaMonkey/2.7.1 MIME-Version: 1.0 To: Jeremy Chadwick References: <20120210145604.Horde.ewjpSpjmRSRPNSH0YRHxgAk@webmail.leidinger.net> <20120210231059.GA25777@icarus.home.lan> <4F3926C5.3010403@gmail.com> <20120213152928.GA74772@icarus.home.lan> In-Reply-To: <20120213152928.GA74772@icarus.home.lan> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Alexander Leidinger , stable@FreeBSD.org Subject: Re: Reducing the need to compile a custom kernel X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Feb 2012 15:38:19 -0000 Jeremy Chadwick wrote: > On Mon, Feb 13, 2012 at 05:05:41PM +0200, Volodymyr Kostyrko wrote: >> Jeremy Chadwick wrote: >>> I want to note here: the pf ALTQ options are a pain in the butt, quite >>> honestly. I've found in the past that removing the ones you don't use >>> won't result in a successful build, thus one must include them all. We >>> do need ALTQ support though, for rate-limiting capability. The NOPCC >>> option is needed for SMP builds, which makes me wonder what the state of >>> SMP is in this regard -- meaning, on non-SMP builds, is it still safe >>> to include ALTQ_NOPCC? >> >> It seems like I'm missing something. What is good about using >> non-SMP kernel? > > Nothing. It's a question of whether or not use of ALTQ_NOPCC causes > breakage on non-SMP kernels, or if FreeBSD even bothers to support > non-SMP at this point. "Non-SMP" means "without options SMP". You got my point. I'm a single core user today but I run SMP-enabled kernel. > Rephrased: if SMP is the default, and "options SMP" works just fine on > systems without multiple processors/cores, then the ALTQ_NOPCC option > should probably be removed. Yep, works for me. However I had found some cruft about extra processing power which would be used in expense of correct work. Can this be something like IPFIREWALL_FORWARD that adds some latency to most cases providing some use only for chosen ones? -- Sphinx of black quartz judge my vow.