From: <cl@rock-chips.com>
To: heiko@sntech.de
Cc: juri.lelli@redhat.com, mark.rutland@arm.com,
geert+renesas@glider.be, peterz@infradead.org,
catalin.marinas@arm.com, bsegall@google.com, will@kernel.org,
mpe@ellerman.id.au, linux@armlinux.org.uk,
dietmar.eggemann@arm.com, ben.dooks@codethink.co.uk,
mgorman@suse.de, Liang Chen <cl@rock-chips.com>,
huangtao@rock-chips.com, keescook@chromium.org,
anshuman.khandual@arm.com, rostedt@goodmis.org,
tglx@linutronix.de, surenb@google.com, mingo@redhat.com,
allison@lohutok.net, linux-arm-kernel@lists.infradead.org,
wad@chromium.org, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, luto@amacapital.net,
george_davis@mentor.com, sudeep.holla@arm.com,
akpm@linux-foundation.org, info@metux.net,
kstewart@linuxfoundation.org
Subject: [PATCH v2 0/1] wait_task_inactive() spend too much time on system startup
Date: Thu, 5 Mar 2020 17:59:47 +0800 [thread overview]
Message-ID: <20200305095948.10873-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.
Liang Chen (1):
sched/fair: do not preempt current task if it is going to call
schedule()
include/linux/sched.h | 5 +++++
kernel/kthread.c | 4 ++++
kernel/sched/fair.c | 13 +++++++++++++
3 files changed, 22 insertions(+)
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-03-05 10:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 9:59 cl [this message]
2020-03-05 9:59 ` [PATCH v2 1/1] sched/fair: do not preempt current task if it is going to call schedule() cl
2020-03-05 17:24 ` Kees Cook
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=20200305095948.10873-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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox