From owner-freebsd-net@FreeBSD.ORG Wed Oct 30 03:30:52 2013 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 589DDA8A; Wed, 30 Oct 2013 03:30:52 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 27DAA2F03; Wed, 30 Oct 2013 03:30:51 +0000 (UTC) Received: from Julian-MBP3.local (ppp121-45-253-246.lns20.per2.internode.on.net [121.45.253.246]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.7) with ESMTP id r9U3UjXT021610 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 29 Oct 2013 20:30:48 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <52707D60.1070001@freebsd.org> Date: Wed, 30 Oct 2013 11:30:40 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: Andre Oppermann , Navdeep Parhar , Luigi Rizzo Subject: Re: MQ Patch. References: <40948D79-E890-4360-A3F2-BEC34A389C7E@lakerest.net> <526FFED9.1070704@freebsd.org> <52701D8B.8050907@freebsd.org> <527022AC.4030502@FreeBSD.org> <527027CE.5040806@freebsd.org> <5270309E.5090403@FreeBSD.org> <5270462B.8050305@freebsd.org> In-Reply-To: <5270462B.8050305@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Randall Stewart , "freebsd-net@freebsd.org" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Oct 2013 03:30:52 -0000 On 10/30/13, 7:35 AM, Andre Oppermann wrote: > > The holy grail so to say would be to run the entire stack with full > affinity up and down. That is certainly possible, provided the > application > is fully aware of it as well. In typical mixed load cases this is > unlikely > the case and the application(s) are floating around. with multithreaded apps it's *most likely* that writes will be coming from several differnent CPUs..