From: Waiman Long <longman@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Tejun Heo <tj@kernel.org>, Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kthread: Export kthread_data()
Date: Tue, 13 Feb 2018 16:42:00 -0500 [thread overview]
Message-ID: <11243edc-22b2-6d07-c2b7-b83a6dd09308@redhat.com> (raw)
In-Reply-To: <7084eed7-5343-f9cc-beda-816c3fae1022@redhat.com>
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
>>> 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
>
BTW, I am fine with not exporting the function. They just have to find
an alternative way of doing it.
-Longman
prev parent reply other threads:[~2018-02-13 21:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 14:52 Waiman Long
2018-02-12 9:24 ` Peter Zijlstra
2018-02-13 15:50 ` Christoph Hellwig
2018-02-13 21:40 ` Waiman Long
2018-02-13 21:42 ` Waiman Long [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=11243edc-22b2-6d07-c2b7-b83a6dd09308@redhat.com \
--to=longman@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®