[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200501190223.GF9191@pick.fieldses.org>
Date: Fri, 1 May 2020 15:02:23 -0400
From: "J. Bruce Fields" <bfields@...hat.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Tejun Heo <tj@...nel.org>,
"open list:NFS, SUNRPC, AND..." <linux-nfs@...r.kernel.org>,
Jeff Layton <jlayton@...hat.com>,
David Howells <dhowells@...hat.com>, Shaohua Li <shli@...com>,
Oleg Nesterov <oleg@...hat.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/4] allow multiple kthreadd's
On Fri, May 01, 2020 at 11:30:38AM -0700, Linus Torvalds wrote:
> On Fri, May 1, 2020 at 11:22 AM Tejun Heo <tj@...nel.org> 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.
Powered by blists - more mailing lists