[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200506153920.GB3350@mtj.thefacebook.com>
Date: Wed, 6 May 2020 11:39:20 -0400
From: Tejun Heo <tj@...nel.org>
To: "J. Bruce Fields" <bfields@...ldses.org>
Cc: "J. Bruce Fields" <bfields@...hat.com>,
Linus Torvalds <torvalds@...ux-foundation.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
Hello, Bruce.
On Wed, May 06, 2020 at 11:36:58AM -0400, J. Bruce Fields wrote:
> On Tue, May 05, 2020 at 05:25:27PM -0400, J. Bruce Fields wrote:
> > On Tue, May 05, 2020 at 05:09:56PM -0400, Tejun Heo wrote:
> > > It's not the end of the world but a bit hacky. I wonder whether something
> > > like the following would work better for identifying worker type so that you
> > > can do sth like
> > >
> > > if (kthread_fn(current) == nfsd)
> > > return kthread_data(current);
> > > else
> > > return NULL;
> >
> > Yes, definitely more generic, looks good to me.
>
> This is what I'm testing with.
>
> If it's OK with you, could I add your Signed-off-by and take it through
> the nfsd tree? I'll have some other patches that will depend on it.
Please feel free to use the code however you see fit. Given that it'll be
originating from you, my signed-off-by might not be the right tag. Something
like Original-patch-by should be good (nothing is fine too).
Thanks.
--
tejun
Powered by blists - more mailing lists