From: Valentin Schneider <valentin.schneider@arm.com>
To: Peter Zijlstra <peterz@infradead.org>, xiaoggchen@tencent.com
Cc: jasperwang@tencent.com, heddchen@tencent.com, mingo@redhat.com,
linux-kernel@vger.kernel.org, tj@kernel.org, lizefan@huawei.com,
hannes@cmpxchg.org, cgroups@vger.kernel.org,
viresh.kumar@linaro.org
Subject: Re: [PATCH 0/5] BT scheduling class
Date: Fri, 21 Jun 2019 14:26:11 +0100 [thread overview]
Message-ID: <6a81a564-9d89-f01d-15b8-e07f092cc5f1@arm.com> (raw)
In-Reply-To: <20190621130316.GK3436@hirez.programming.kicks-ass.net>
On 21/06/2019 14:03, Peter Zijlstra wrote:
> On Fri, Jun 21, 2019 at 03:45:52PM +0800, xiaoggchen@tencent.com wrote:
>
>> First only server application exists in the system and the success
>> rate is 99.998% and the average cpu use is only 25%.
>
> Have you guys looked at this series:
>
> https://lkml.kernel.org/r/cover.1556182964.git.viresh.kumar@linaro.org
>
>
Sort of a shot in the dark here, but I wonder if task stealing [1] could
help as well? IIRC Steve had some pretty good CPU utilization improvements
with his series.
FWIW I have a somewhat recent rebase of CFS stealing laying around at [2].
[1]: https://lore.kernel.org/lkml/1544131696-2888-1-git-send-email-steven.sistare@oracle.com/
[2]: http://www.linux-arm.org/git?p=linux-vs.git;a=shortlog;h=refs/heads/mainline/cfs-stealing/v4-rebase
prev parent reply other threads:[~2019-06-21 13:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 7:45 xiaoggchen
2019-06-21 7:45 ` [PATCH 1/5] sched/BT: add BT scheduling entity xiaoggchen
2019-06-21 7:45 ` [PATCH 2/5] sched/BT: implement the BT scheduling class xiaoggchen
2019-06-21 7:45 ` [PATCH 3/5] sched/BT: extend the priority for " xiaoggchen
2019-06-21 7:45 ` [PATCH 4/5] sched/BT: account the cpu time " xiaoggchen
2019-06-21 7:45 ` [PATCH 5/5] sched/BT: add debug information " xiaoggchen
2019-06-21 12:36 ` [PATCH 0/5] " Peter Zijlstra
2019-06-21 13:03 ` Peter Zijlstra
2019-06-21 13:26 ` Valentin Schneider [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=6a81a564-9d89-f01d-15b8-e07f092cc5f1@arm.com \
--to=valentin.schneider@arm.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=heddchen@tencent.com \
--cc=jasperwang@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tj@kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=xiaoggchen@tencent.com \
/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
all inboxes | Powered by JetHome®