From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 21:15:29 2014 Return-Path: Delivered-To: freebsd-stable@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 ESMTPS id 5737E7FE for ; Wed, 11 Jun 2014 21:15:29 +0000 (UTC) Received: from mail-qc0-x236.google.com (mail-qc0-x236.google.com [IPv6:2607:f8b0:400d:c01::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 192B72759 for ; Wed, 11 Jun 2014 21:15:29 +0000 (UTC) Received: by mail-qc0-f182.google.com with SMTP id m20so586261qcx.27 for ; Wed, 11 Jun 2014 14:15:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=vDTxGOGbWh/sy4rFyqU1nUMgIsQqgrcU+hkxKTFrnII=; b=0Q1uv46NcBbVhlDPXfcvQi8nBSzKb7erLr99t0Ia5lXxBwNwth9QHi0d+7pLlDsRlx o8SUzDC45j/cv2+RBLXog6TGQYGQWGISHdMDIyCLCVr6nO5h0oHw9MBy7ldeOQIXoEEE +eMJ5ZtC41oqVCRypoNvhiIgNgaXHqsRGkdA68e/O7JdcLPAWm03j40iLLGM8IsihY/Y 8IdUps2z5JQQdlH6o/nw5x42zL0t2S+p0IwLTX5iYa958KA8FhKF+1o1BX0kGkdzvnth fjW3zPQXIYCK2kpVTKnJg25pBsfYrNtaXdzKUcRNz0+RD0x5PZ08UhLDrGpZP4aeWKq3 Gthw== MIME-Version: 1.0 X-Received: by 10.140.25.166 with SMTP id 35mr26001471qgt.103.1402521328173; Wed, 11 Jun 2014 14:15:28 -0700 (PDT) Received: by 10.96.73.39 with HTTP; Wed, 11 Jun 2014 14:15:28 -0700 (PDT) In-Reply-To: References: Date: Wed, 11 Jun 2014 14:15:28 -0700 Message-ID: Subject: Re: dedicate the most available cpu cores to my application From: hiren panchasara To: Nick Sivo Content-Type: text/plain; charset=UTF-8 Cc: Mahdi Dashtbozorgi , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jun 2014 21:15:29 -0000 On Wed, Jun 11, 2014 at 1:16 PM, Nick Sivo wrote: > I'd actually like to do the opposite of this, and have run into the > same problem. > > cpuset -s 1 -l 0 > cpuset: setaffinity: Resource deadlock avoided I see the same problem on -CURRENT. fwiw, a fix is being discussed and worked on: http://lists.freebsd.org/pipermail/freebsd-hackers/2014-June/045292.html I am going to try and apply the proposed patch https://phabric.freebsd.org/D141 to see how it behaves. cheers, Hiren