From: <cl@rock-chips.com>
To: heiko@sntech.de
Cc: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
akpm@linux-foundation.org, tglx@linutronix.de,
mpe@ellerman.id.au, surenb@google.com, ben.dooks@codethink.co.uk,
anshuman.khandual@arm.com, catalin.marinas@arm.com,
will@kernel.org, keescook@chromium.org, luto@amacapital.net,
wad@chromium.org, mark.rutland@arm.com, geert+renesas@glider.be,
george_davis@mentor.com, sudeep.holla@arm.com,
linux@armlinux.org.uk, gregkh@linuxfoundation.org,
info@metux.net, kstewart@linuxfoundation.org,
allison@lohutok.net, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, huangtao@rock-chips.com,
Liang Chen <cl@rock-chips.com>
Subject: [PATCH v3 0/1] wait_task_inactive() spend too much time on system startup
Date: Fri, 6 Mar 2020 15:01:32 +0800 [thread overview]
Message-ID: <20200306070133.18335-1-cl@rock-chips.com> (raw)
From: Liang Chen <cl@rock-chips.com>
Changelog:
v1: wait_task_inactive() frequently call schedule_hrtimeout() and spend a lot of time,
i am trying to optimize it on rockchip platform.
v2: Use atomic_flags(PFA) instead of TIF flag, and add some comments.
v3: Use a new method fix this issue to make the code simple.
Liang Chen (1):
kthread: do not preempt current task if it is going to call schedule()
kernel/kthread.c | 17 +++++++++++++++--
1 file changed, 15 insertions(+), 2 deletions(-)
--
2.17.1
next reply other threads:[~2020-03-06 7:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 7:01 cl [this message]
2020-03-06 7:01 ` [PATCH v3 1/1] kthread: do not preempt current task if it is going to call schedule() cl
2020-03-06 17:09 ` Steven Rostedt
2020-03-06 17:09 ` Steven Rostedt
2020-03-11 15:39 ` Peter Zijlstra
2020-03-11 15:39 ` Peter Zijlstra
2020-03-20 12:58 ` [tip: sched/core] kthread: Do " tip-bot2 for Liang Chen
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=20200306070133.18335-1-cl@rock-chips.com \
--to=cl@rock-chips.com \
--cc=akpm@linux-foundation.org \
--cc=allison@lohutok.net \
--cc=anshuman.khandual@arm.com \
--cc=ben.dooks@codethink.co.uk \
--cc=bsegall@google.com \
--cc=catalin.marinas@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=geert+renesas@glider.be \
--cc=george_davis@mentor.com \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=info@metux.net \
--cc=juri.lelli@redhat.com \
--cc=keescook@chromium.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=luto@amacapital.net \
--cc=mark.rutland@arm.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sudeep.holla@arm.com \
--cc=surenb@google.com \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.org \
--cc=wad@chromium.org \
--cc=will@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.