From owner-freebsd-net@FreeBSD.ORG Tue Jun 24 20:56:05 2014 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 00BAEB8F for ; Tue, 24 Jun 2014 20:56:04 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DC6022D31 for ; Tue, 24 Jun 2014 20:56:04 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s5OKu4bi037170 for ; Tue, 24 Jun 2014 21:56:04 +0100 (BST) (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 190785] [em] cpu affinity not working in FreeBSD 10-STABLE Date: Tue, 24 Jun 2014 20:56:05 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: gondim@bsdinfo.com.br X-Bugzilla-Status: Issue Resolved X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2014 20:56:05 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190785 --- Comment #8 from gondim@bsdinfo.com.br --- Yes it changes the CPU. With top -PSH you can see it changing CPU. I did: cpuset -x 264 -l 3 See my top below: PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU COMMAND 10 root 155 ki31 0K 64K RUN 1 477.6H 100.00% idle{idle: cpu1} 0 root -92 0 0K 384K CPU3 3 219.2H 60.50% kernel{em0 que} PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU COMMAND 10 root 155 ki31 0K 64K RUN 1 477.6H 100.00% idle{idle: cpu1} 0 root -92 0 0K 384K CPU2 2 219.2H 61.72% kernel{em0 que} Process kernel{em0 que} running in CPU3 and CPU2. -- You are receiving this mail because: You are the assignee for the bug.