From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
tglx@linutronix.de
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Andy Lutomirski <luto@kernel.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>,
Daniel Bristot de Oliveira <bristot@redhat.com>
Subject: Re: [PATCH 0/8] kernel/fork: Move thread stack free otu of the scheduler path.
Date: Mon, 13 Dec 2021 16:18:32 +0100 [thread overview]
Message-ID: <YbdkSLFdBL/xeRbA@linutronix.de> (raw)
In-Reply-To: <20211203162211.qvcnvbj4cdsa5g3a@linutronix.de>
On 2021-12-03 17:22:13 [+0100], To linux-kernel@vger.kernel.org wrote:
> On 2021-11-18 15:38:50 [+0100], To linux-kernel@vger.kernel.org wrote:
> > + tglx.
> >
> > It starts at
> > https://lore.kernel.org/all/20211118143452.136421-1-bigeasy@linutronix.de/
> >
> > On 2021-11-18 15:34:44 [+0100], To linux-kernel@vger.kernel.org wrote:
> > >
> > > This is a follup-up on the patch
> > > sched: Delay task stack freeing on RT
> > > https://lkml.kernel.org/r/20210928122411.593486363@linutronix.de
> > >
> > > It addresses the review feedback:
> > > - Decouple stack accounting from its free invocation. The accounting
> > > happens in do_exit(), the final free call happens later.
> > >
> > > - Add put_task_stack_sched() to finish_task_switch(). Here the VMAP
> > > stack is cached only. If it fails, or in the !VMAP case then the final
> > > free happens in delayed_put_task_struct(). This is also an oportunity
> > > to cache the stack.
>
> ping ;)
ping.
Sebastian
prev parent reply other threads:[~2021-12-13 15:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 14:34 [PATCH 0/8] kernel/fork: Move thread stack free otu of the scheduler path Sebastian Andrzej Siewior
2021-11-18 14:34 ` [PATCH 1/8] kernel/fork: Redo ifdefs around task's handling Sebastian Andrzej Siewior
2021-11-18 14:34 ` [PATCH 2/8] kernel/fork: Duplicate task_struct before stack allocation Sebastian Andrzej Siewior
2021-11-18 14:34 ` [PATCH 3/8] kernel/fork, IA64: Provide a alloc_thread_stack_node() for IA64 Sebastian Andrzej Siewior
2021-11-18 14:34 ` [PATCH 4/8] kernel/fork: Don't assign the stack pointer in dup_task_struct() Sebastian Andrzej Siewior
2021-11-18 14:34 ` [PATCH 5/8] kernel/fork: Move memcg_charge_kernel_stack() into CONFIG_VMAP_STACK Sebastian Andrzej Siewior
2021-11-18 14:34 ` [PATCH 6/8] kernel/fork: Move task stack account to do_exit() Sebastian Andrzej Siewior
2021-11-18 14:34 ` [PATCH 7/8] kernel/fork: Only cache the VMAP stack in finish_task_switch() Sebastian Andrzej Siewior
2021-11-18 14:34 ` [PATCH 8/8] kernel/fork: Use IS_ENABLED() in account_kernel_stack() Sebastian Andrzej Siewior
2021-11-18 14:38 ` [PATCH 0/8] kernel/fork: Move thread stack free otu of the scheduler path Sebastian Andrzej Siewior
2021-12-03 16:22 ` Sebastian Andrzej Siewior
2021-12-13 15:18 ` Sebastian Andrzej Siewior [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=YbdkSLFdBL/xeRbA@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.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;
as well as URLs for NNTP newsgroup(s).