From: Christian Brauner <brauner@kernel.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: NeilBrown <neilb@suse.de>, Al Viro <viro@zeniv.linux.org.uk>,
Jens Axboe <axboe@kernel.dk>,
Chuck Lever <chuck.lever@oracle.com>,
Jeff Layton <jlayton@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH/RFC] core/nfsd: allow kernel threads to use task_work.
Date: Tue, 28 Nov 2023 16:33:28 +0100 [thread overview]
Message-ID: <20231128-elastisch-freuden-f9de91041218@brauner> (raw)
In-Reply-To: <20231128135258.GB22743@redhat.com>
On Tue, Nov 28, 2023 at 02:52:59PM +0100, Oleg Nesterov wrote:
> On 11/28, Christian Brauner wrote:
> >
> > Should be simpler if you invert the logic?
> >
> > COMPLETELY UNTESTED
>
> Agreed, this looks much better to me. But perhaps we can just add the new
> PF_KTHREAD_XXX flag and change fput
>
>
> --- a/fs/file_table.c
> +++ b/fs/file_table.c
> @@ -445,7 +445,8 @@ void fput(struct file *file)
> if (atomic_long_dec_and_test(&file->f_count)) {
> struct task_struct *task = current;
>
> - if (likely(!in_interrupt() && !(task->flags & PF_KTHREAD))) {
> + if (likely(!in_interrupt() &&
> + task->flags & (PF_KTHREAD|PF_KTHREAD_XXX) != PF_KTHREAD) {
> init_task_work(&file->f_rcuhead, ____fput);
> if (!task_work_add(task, &file->f_rcuhead, TWA_RESUME))
> return;
>
> ?
>
> Then nfsd() can simply set PF_KTHREAD_XXX. This looks even simpler to me.
Yeah, I had played with that as well. Only reason I didn't do it was to
avoid a PF_* flag. If that's preferable it might be worth to just add
PF_TASK_WORK and decouple this from PF_KTHREAD. kthread creation and
userspace process creation are all based on the same struct
kernel_clone_args for a while now ever since we added this for clone3()
so we catch everything in copy_process():
diff --git a/fs/file_table.c b/fs/file_table.c
index 6deac386486d..5d3eb5ef4fc7 100644
--- a/fs/file_table.c
+++ b/fs/file_table.c
@@ -437,7 +437,7 @@ void fput(struct file *file)
file_free(file);
return;
}
- if (likely(!in_interrupt() && !(task->flags & PF_KTHREAD))) {
+ if (likely(!in_interrupt() && (task->flags & PF_TASK_WORK))) {
init_task_work(&file->f_rcuhead, ____fput);
if (!task_work_add(task, &file->f_rcuhead, TWA_RESUME))
return;
diff --git a/include/linux/sched.h b/include/linux/sched.h
index 292c31697248..8dfc06acc6a0 100644
--- a/include/linux/sched.h
+++ b/include/linux/sched.h
@@ -1755,7 +1755,7 @@ extern struct pid *cad_pid;
* I am cleaning dirty pages from some other bdi. */
#define PF_KTHREAD 0x00200000 /* I am a kernel thread */
#define PF_RANDOMIZE 0x00400000 /* Randomize virtual address space */
-#define PF__HOLE__00800000 0x00800000
+#define PF_TASK_WORK 0x00800000
#define PF__HOLE__01000000 0x01000000
#define PF__HOLE__02000000 0x02000000
#define PF_NO_SETAFFINITY 0x04000000 /* Userland is not allowed to meddle with cpus_mask */
diff --git a/kernel/fork.c b/kernel/fork.c
index 10917c3e1f03..2604235c800f 100644
--- a/kernel/fork.c
+++ b/kernel/fork.c
@@ -2346,6 +2346,14 @@ __latent_entropy struct task_struct *copy_process(
if (args->io_thread)
p->flags |= PF_IO_WORKER;
+ /*
+ * By default only non-kernel threads can use task work. Kernel
+ * threads that manage task work explicitly can add that flag in
+ * their kthread callback.
+ */
+ if (!args->kthread)
+ p->flags |= PF_TASK_WORK;
+
if (args->name)
strscpy_pad(p->comm, args->name, sizeof(p->comm));
next prev parent reply other threads:[~2023-11-28 15:33 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 22:05 [PATCH/RFC] core/nfsd: allow kernel threads to use task_work NeilBrown
2023-11-27 22:30 ` Al Viro
2023-11-27 22:43 ` NeilBrown
2023-11-27 22:59 ` Chuck Lever
2023-11-28 0:16 ` NeilBrown
2023-11-28 1:37 ` Chuck Lever
2023-11-28 2:57 ` NeilBrown
2023-11-28 15:34 ` Chuck Lever
2023-11-30 17:50 ` Jeff Layton
2023-11-28 13:51 ` Christian Brauner
2023-11-28 14:15 ` Jeff Layton
2023-11-28 15:22 ` Chuck Lever
2023-11-28 23:31 ` NeilBrown
2023-11-28 23:20 ` NeilBrown
2023-11-29 11:43 ` Christian Brauner
2023-12-04 1:30 ` NeilBrown
2023-11-29 14:04 ` Chuck Lever
2023-11-30 17:47 ` Jeff Layton
2023-11-30 18:07 ` Chuck Lever
2023-11-30 18:33 ` Jeff Layton
2023-11-28 11:24 ` Christian Brauner
2023-11-28 13:52 ` Oleg Nesterov
2023-11-28 15:33 ` Christian Brauner [this message]
2023-11-28 16:59 ` Oleg Nesterov
2023-11-28 17:29 ` Oleg Nesterov
2023-11-28 23:40 ` NeilBrown
2023-11-29 11:38 ` Christian Brauner
2023-11-28 14:01 ` Oleg Nesterov
2023-11-28 14:20 ` Oleg Nesterov
2023-11-29 0:14 ` NeilBrown
2023-11-29 7:55 ` Oleg Nesterov
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=20231128-elastisch-freuden-f9de91041218@brauner \
--to=brauner@kernel.org \
--cc=axboe@kernel.dk \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=juri.lelli@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=neilb@suse.de \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=vincent.guittot@linaro.org \
--cc=viro@zeniv.linux.org.uk \
/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