Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp968168ybz; Fri, 1 May 2020 11:50:14 -0700 (PDT) X-Google-Smtp-Source: APiQypJX+UI7lYL+CkbmjxFMbk/+9rjbO5PFUXGSiTRb4wTjRndJ5337pOxDKELq9hRhXn99oYNv X-Received: by 2002:a17:906:7f0d:: with SMTP id d13mr4643457ejr.312.1588359014131; Fri, 01 May 2020 11:50:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1588359014; cv=none; d=google.com; s=arc-20160816; b=ALDqJFUf4JSVXbswahPxIKmq/vgDIYXYb8AB/73g9TlYU2ZOUhgTFSUsGWMYRCBY+S mkSouWfzMkVWneJqHCjEHFaCAm6LIdtHsLoKmtLSqLYCFFt95+34J/i4EhWVlivI5jLn pQ0mxT9Dl8KUktSawRhe9O5oaN3fHxKoenK62f/BHANuQZrZgbFsjU9xClTyIeVf92IP WWmnvNx4soYM3/2chhEnFWwWpgxD7Ljaa5VEHf0McwQMd4M0yZcIzXbfiS2W5VnA/Tmw qWOJ51//w1ubFZknQVDOAybszOzESFpw7ldgyVtbCGTIgT/WfEIsB1wA//qbs1NELPIN 1XPA== 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=UWBw6vpYtZb0E4Qraw0yWbVU2/WZXleDlQcMtBsJSWY=; b=frp1yPLZrnYzqRKTJsAIvGvPPeqrmUk7YNAqyV4gFIJYEfkxSU+7BiWI16vFOZmcPp GO3TiDgqJWLPgtk4Ke4SPlmaIbYNSC4nCboXG0pxjQER6emZn+rN3g4NF/ZGpFEG4uFv GFO8zPRw/49YoqZqXH3+jT4F7xn+1RVr8luC567gd01LUI5YGNW6RG3tt7l0Hanit6m2 SH6PmKx5ly9dadnPNGLP8OEONy3xQk8rwVXc9egkl61wfaH1Lqajpuk8UVXMteHfMFTW YcsnddzJ5xDyrrB8aUvYxy6RNyUz37wpF9nZ9akvKdVgjDP6YppBgJZAteSmBVHF9u5D Holw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=SB0oRYCk; spf=pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-nfs-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 f12si2131862edq.119.2020.05.01.11.49.45; Fri, 01 May 2020 11:50:14 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-nfs-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=SB0oRYCk; spf=pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-nfs-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 S1729779AbgEASto (ORCPT + 99 others); Fri, 1 May 2020 14:49:44 -0400 Received: from us-smtp-1.mimecast.com ([207.211.31.81]:39733 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1729721AbgEAStn (ORCPT ); Fri, 1 May 2020 14:49:43 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1588358982; 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=UWBw6vpYtZb0E4Qraw0yWbVU2/WZXleDlQcMtBsJSWY=; b=SB0oRYCk6LQGoFHQ56Z1ZAe7qLw+DHJ8XxLIB7Z+th2LYE+dJsekT3yffvkjyCeEZQzoSe 78fKbTAqYmNnG6LTrpnYXEt37f2PnpGDaudUGgbbCyZoI/EYOF/IxxAva1UPLvn+mgOksd Eg02el6WGj+tXjMSeAf93hoEPRKbNa8= 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-511-Y0Qb86jFM8G7mChzPLlpow-1; Fri, 01 May 2020 14:49:40 -0400 X-MC-Unique: Y0Qb86jFM8G7mChzPLlpow-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 7107045F; Fri, 1 May 2020 18:49:39 +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 B227B6084A; Fri, 1 May 2020 18:49:36 +0000 (UTC) Received: by pick.fieldses.org (Postfix, from userid 2815) id BDE851202A6; Fri, 1 May 2020 14:49:35 -0400 (EDT) Date: Fri, 1 May 2020 14:49:35 -0400 From: "J. Bruce Fields" To: Tejun Heo Cc: Linus Torvalds , "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: <20200501184935.GD9191@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: <20200501182154.GG5462@mtj.thefacebook.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 Sender: linux-nfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org On Fri, May 01, 2020 at 02:21:54PM -0400, Tejun Heo wrote: > Hello, > > On Fri, May 01, 2020 at 10:59:24AM -0700, Linus Torvalds wrote: > > Which kind of makes me want to point a finger at Tejun. But it's been > > mostly PeterZ touching this file lately.. > > 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. Pretty much. > Can't that be done with kthread_data()? Huh, maybe so, thanks. I need to check this from generic file locking code that could be run by any task--but I assume there's an easy way I can check if I'm a kthread before calling kthread_data(current). I do expect to expose a delegation interface for userspace servers eventually too. But we could do the tgid check for them and still use kthread_data() for nfsd. That might work. --b.