Re: [PATCH] kthread: Export kthread_data()

2018-02-13 Thread Waiman Long
On 02/13/2018 04:40 PM, Waiman Long wrote: > On 02/13/2018 10:50 AM, Christoph Hellwig wrote: >> On Fri, Feb 09, 2018 at 09:52:21AM -0500, Waiman Long wrote: >>> When multiple kernel threads are created to cooperatively work on >>> a common task, we may need a convenient way to access data that are

Re: [PATCH] kthread: Export kthread_data()

2018-02-13 Thread Waiman Long
On 02/13/2018 10:50 AM, Christoph Hellwig wrote: > On Fri, Feb 09, 2018 at 09:52:21AM -0500, Waiman Long wrote: >> When multiple kernel threads are created to cooperatively work on >> a common task, we may need a convenient way to access data that are >> specific to each kthread. >> >> The kthread_

Re: [PATCH] kthread: Export kthread_data()

2018-02-13 Thread Christoph Hellwig
On Fri, Feb 09, 2018 at 09:52:21AM -0500, Waiman Long wrote: > When multiple kernel threads are created to cooperatively work on > a common task, we may need a convenient way to access data that are > specific to each kthread. > > The kthread_data() function fits this need. However, it was not >

Re: [PATCH] kthread: Export kthread_data()

2018-02-12 Thread Peter Zijlstra
On Fri, Feb 09, 2018 at 09:52:21AM -0500, Waiman Long wrote: > When multiple kernel threads are created to cooperatively work on > a common task, we may need a convenient way to access data that are > specific to each kthread. > > The kthread_data() function fits this need. However, it was not >

[PATCH] kthread: Export kthread_data()

2018-02-09 Thread Waiman Long
When multiple kernel threads are created to cooperatively work on a common task, we may need a convenient way to access data that are specific to each kthread. The kthread_data() function fits this need. However, it was not visible to kthreads started in a kernel module. To solve this problem, th