[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7084eed7-5343-f9cc-beda-816c3fae1022@redhat.com>
Date: Tue, 13 Feb 2018 16:40:34 -0500
From: Waiman Long <longman@...hat.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Tejun Heo <tj@...nel.org>, Ingo Molnar <mingo@...nel.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kthread: Export kthread_data()
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_data() function fits this need. However, it was not
>> visible to kthreads started in a kernel module. To solve this problem,
>> the kthread_data() function is now exported allowing kthreads from
>> kernel modules to use it.
> Please send this along wit hthe actual user of it.
It is the developers of the dm-vdo/kvdo modules that would like to use
the kthread_data() function. See
https://github.com/dm-vdo/kvdo
Those modules have a bunch of kernel threads working on block storage
deduplication/compression.
-Longman
Powered by blists - more mailing lists