public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
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

             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$(echo .)com \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=allison@lohutok$(echo .)net \
    --cc=anshuman.khandual@arm$(echo .)com \
    --cc=ben.dooks@codethink$(echo .)co.uk \
    --cc=bsegall@google$(echo .)com \
    --cc=catalin.marinas@arm$(echo .)com \
    --cc=dietmar.eggemann@arm$(echo .)com \
    --cc=geert+renesas@glider$(echo .)be \
    --cc=george_davis@mentor$(echo .)com \
    --cc=gregkh@linuxfoundation$(echo .)org \
    --cc=heiko@sntech$(echo .)de \
    --cc=huangtao@rock-chips$(echo .)com \
    --cc=info@metux$(echo .)net \
    --cc=juri.lelli@redhat$(echo .)com \
    --cc=keescook@chromium$(echo .)org \
    --cc=kstewart@linuxfoundation$(echo .)org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux@armlinux$(echo .)org.uk \
    --cc=luto@amacapital$(echo .)net \
    --cc=mark.rutland@arm$(echo .)com \
    --cc=mgorman@suse$(echo .)de \
    --cc=mingo@redhat$(echo .)com \
    --cc=mpe@ellerman$(echo .)id.au \
    --cc=peterz@infradead$(echo .)org \
    --cc=rostedt@goodmis$(echo .)org \
    --cc=sudeep.holla@arm$(echo .)com \
    --cc=surenb@google$(echo .)com \
    --cc=tglx@linutronix$(echo .)de \
    --cc=wad@chromium$(echo .)org \
    --cc=will@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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