NetBSD Problem Report #56968

From www@netbsd.org  Wed Aug 17 04:18:18 2022
Return-Path: <www@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 047091A921F
	for <gnats-bugs@gnats.NetBSD.org>; Wed, 17 Aug 2022 04:18:18 +0000 (UTC)
Message-Id: <20220817041816.D08571A923A@mollari.NetBSD.org>
Date: Wed, 17 Aug 2022 04:18:16 +0000 (UTC)
From: thorpej@me.com
Reply-To: thorpej@me.com
To: gnats-bugs@NetBSD.org
Subject: I have kernel threads sitting in carp_wqinput (x NCPU) even through I'm not using CARP
X-Send-Pr-Version: www-1.0

>Number:         56968
>Category:       kern
>Synopsis:       I have kernel threads sitting in carp_wqinput (x NCPU) even through I'm not using CARP
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Aug 17 04:20:00 +0000 2022
>Originator:     Jason Thorpe
>Release:        NetBSD 9.99.99
>Organization:
RISCy Business
>Environment:
This machine: https://dmesgd.nycbug.org/index.cgi?do=view&id=6646
>Description:
I'm not using CARP, but I have a bunch of kernel threads waiting to handle CARP input -- one per CPU core.  This is an annoying waste of system resources.
>How-To-Repeat:
Boot the system.
>Fix:
threadpool-based workqueue?  (That might not be the best solution for all cases of workqueue, tho.). At the very least, defer creation of the wqinput stuff for CARP until someone actually shows intent to use it.

Home	PR Database Search