From owner-freebsd-bugs@freebsd.org  Thu Oct  5 06:25:16 2017
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2649EE2DF5F
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Thu,  5 Oct 2017 06:25:16 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 1263721F7
 for <freebsd-bugs@FreeBSD.org>; Thu,  5 Oct 2017 06:25:16 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v956PFvR054889
 for <freebsd-bugs@FreeBSD.org>; Thu, 5 Oct 2017 06:25:15 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 222789] IRQ pinning is not working as expected with cpuset -x
Date: Thu, 05 Oct 2017 06:25:16 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: bhargava.marreddy@broadcom.com
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
 op_sys bug_status bug_severity priority component assigned_to reporter
Message-ID: <bug-222789-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Oct 2017 06:25:16 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222789

            Bug ID: 222789
           Summary: IRQ pinning is not working as expected with cpuset -x
           Product: Base System
           Version: CURRENT
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: bhargava.marreddy@broadcom.com

Can some please guide me in configuring IRQ pinning for Network driver?

Looks like IRQ pinning is not working as expected with cpuset command.

This is what I=E2=80=99m doing ..

1. Identify the IRQ number on rxq0
# vmstat -i | grep rxq0
irq271: bnxt0:rxq0 2 0

2. Read the current affinity mask:
#cpuset -g -x 271
irq 271 mask: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17,=
 18,
19, 20, 21, 22, 23

3. Set CPU2 for IRQ 271
# cpuset -l 2 -x 271

4. Make sure by reading back ..
# cpuset -g -x 271
irq 271 mask: 2

5. Start TCP traffic, interrupts will be coming into IRQ 271 (rxq0) but
different CPU will be processing then (but not CPU 2).
As per =E2=80=98top =E2=80=93P=E2=80=99, cpu 2 is 100% free and different c=
pu is ~100% busy.

Thanks,
Chenna.

--=20
You are receiving this mail because:
You are the assignee for the bug.=