From owner-freebsd-stable@FreeBSD.ORG Thu Dec 22 19:01:23 2011 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9B21F1065672 for ; Thu, 22 Dec 2011 19:01:23 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id E0F4B8FC1F for ; Thu, 22 Dec 2011 19:01:22 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id VAA20569; Thu, 22 Dec 2011 21:01:18 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1RdntF-0000B8-Mq; Thu, 22 Dec 2011 21:01:17 +0200 Message-ID: <4EF37E7B.4020505@FreeBSD.org> Date: Thu, 22 Dec 2011 21:01:15 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:8.0) Gecko/20111206 Thunderbird/8.0 MIME-Version: 1.0 To: Steve Kargl References: <4EE1EAFE.3070408@m5p.com> <20111215215554.GA87606@troutmask.apl.washington.edu> <20111222005250.GA23115@troutmask.apl.washington.edu> <20111222103145.GA42457@onelab2.iet.unipi.it> <20111222184531.GA36084@troutmask.apl.washington.edu> In-Reply-To: <20111222184531.GA36084@troutmask.apl.washington.edu> X-Enigmail-Version: undefined Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org Subject: Re: SCHED_ULE should not be the default 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: Thu, 22 Dec 2011 19:01:23 -0000 on 22/12/2011 20:45 Steve Kargl said the following: > I've used schedgraph to look at the ktrdump output. A jpg is > available at http://troutmask.apl.washington.edu/~kargl/freebsd/ktr.jpg > This shows the ping-pong effect where here 3 processes appear to be > using 2 cpus while the remaining 2 processes are pinned to their > cpus. I'd recommended enabling CPU-specific background colors via the menu in schedgraph for a better illustration of your findings. NB: I still don't understand the point of purposefully running N+1 CPU-bound processes. -- Andriy Gapon