Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp980111ybz; Fri, 1 May 2020 12:04:52 -0700 (PDT) X-Google-Smtp-Source: APiQypL+Yui5vQkTpPEEW/Og6H5MylpiV1MH144yfdkMt+jprPj7x7cPCCHJuxMkT2sFfS++2MGI X-Received: by 2002:aa7:df8d:: with SMTP id b13mr4891724edy.145.1588359892706; Fri, 01 May 2020 12:04:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1588359892; cv=none; d=google.com; s=arc-20160816; b=I3QGe4b3ZL41PzwQzRBrBMkxZG/XIwcxmmc/Z+ErfIJ6nNQIATYczElD3L5E5QEh9H mshh/StG+P5gAIaiF3Om5josq7Oru1TfVmpPUSkfvwqiKRMBpPTbOBHBRqNFoUIuMLH/ 9UHSea4yhkr3gaM+jx113J+9rmizH6oS2vUWhzh9OepzejsGMa2DDyM5yvbulrZPr9Xx yxv0obx94R7x3b87xpLxCQkBX5qO+Z9SmXdpVcKACorewN7bg0KKOY9pDYJ8Htyb4No2 jRJcrEmo//wPqHQpBXt5uRPJx7VsJtJRLbx+R4d/42o6CQcRsUYOG7kQu9Xy4o6ByLlC z2yA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=Jek6f1FrZy1FOjnEBD+3htgOWCPMzgLS9uHoe5URBjs=; b=WRe4UwcNDnKLdg1UHYdF4pNOf/eBczug+L/3tq6ww1DJDR1njLuuI33+FqBvX6DC25 rhO5XcQ41AsO0H2/VD/W24lKWYqFekOgfGf1OONmZ+diriAjMHq0iV9WtgyTaOtfDWFM lmddgY0iIEsRdzahAwM5PaHp7D0G4xNG6Ya5Fnj3VfkCH4DwDfYZRbqZRKP4cStVXKxx 4fg0bOibV+B53Fxk92bmH/wUO+rv5B2MI14gxp1TfBMWmxBVeBvfJnF919tanfgOjoTj 0ChOVbBgrD5BoTyob+91CVEzQIUBmXNAns5WSJwk3jT1Mz8VIAXQCzJBKA7wCwCesXR1 cNmA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=hL1KTYBV; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id d16si1980121eds.428.2020.05.01.12.04.28; Fri, 01 May 2020 12:04:52 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=hL1KTYBV; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730464AbgEATCd (ORCPT + 99 others); Fri, 1 May 2020 15:02:33 -0400 Received: from us-smtp-delivery-1.mimecast.com ([207.211.31.120]:46378 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1730449AbgEATCd (ORCPT ); Fri, 1 May 2020 15:02:33 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1588359752; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Jek6f1FrZy1FOjnEBD+3htgOWCPMzgLS9uHoe5URBjs=; b=hL1KTYBVPAK7yBBqk6ZJYKqytNYGAmsmJROy6ndg9C5mp9esANedmz0cj8Mr4Bzbh4kBwa dofabrozqC4FYxENVHru7MQstVNZLuQRWA1nctmcDSWwoKanlR1eGwR/IJnB7qZae37yTW NqS5ff8fvSiTrq0LLO/duU0RefvNoN8= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-273-PJVo74boNAOibribiK5KtQ-1; Fri, 01 May 2020 15:02:28 -0400 X-MC-Unique: PJVo74boNAOibribiK5KtQ-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 83029107ACF4; Fri, 1 May 2020 19:02:27 +0000 (UTC) Received: from pick.fieldses.org (ovpn-114-161.phx2.redhat.com [10.3.114.161]) by smtp.corp.redhat.com (Postfix) with ESMTPS id A6F0438A; Fri, 1 May 2020 19:02:24 +0000 (UTC) Received: by pick.fieldses.org (Postfix, from userid 2815) id B9B2A1202A6; Fri, 1 May 2020 15:02:23 -0400 (EDT) Date: Fri, 1 May 2020 15:02:23 -0400 From: "J. Bruce Fields" To: Linus Torvalds Cc: Tejun Heo , "open list:NFS, SUNRPC, AND..." , Jeff Layton , David Howells , Shaohua Li , Oleg Nesterov , Linux Kernel Mailing List Subject: Re: [PATCH 0/4] allow multiple kthreadd's Message-ID: <20200501190223.GF9191@pick.fieldses.org> References: <1588348912-24781-1-git-send-email-bfields@redhat.com> <20200501182154.GG5462@mtj.thefacebook.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 01, 2020 at 11:30:38AM -0700, Linus Torvalds wrote: > On Fri, May 1, 2020 at 11:22 AM Tejun Heo wrote: > > > > Looks fine to me too. I don't quite understand the usecase tho. It looks > > like all it's being used for is to tag some kthreads as belonging to the > > same group. Can't that be done with kthread_data()? > > I _think_ Bruce wants the signal handling unification too, because > nfsd wants to react to being shut down with signals. No, maybe kthread_data() might do the job. (I don't see how this would help with signal handling. But, I'm kind of ignorant of how signalling works.) --b.