From: Tejun Heo <tj@kernel.org>
To: Jan Kara <jack@suse.cz>
Cc: axboe@kernel.dk, linux-kernel@vger.kernel.org,
Jeff Moyer <jmoyer@redhat.com>, Jan Kara <jack@suse.com>
Subject: Re: [PATCH 5/5] cfq-iosched: Allow parent cgroup to preempt its child
Date: Fri, 8 Jan 2016 13:17:48 -0500 [thread overview]
Message-ID: <20160108181748.GY1898@mtj.duckdns.org> (raw)
In-Reply-To: <1452180496-18483-6-git-send-email-jack@suse.cz>
Hello,
On Thu, Jan 07, 2016 at 04:28:16PM +0100, Jan Kara wrote:
> From: Jan Kara <jack@suse.com>
>
> Currently we don't allow sync workload of one cgroup to preempt sync
> workload of any other cgroup. This is because we want to achieve service
> separation between cgroups. However in cases where cgroup preempting is
> ancestor of the current cgroup, there is no need of separation and
> idling introduces unnecessary overhead. This is hurts for example the
^^^
> case when workload is isolated within a cgroup but journalling threads
> are in root cgroup. Simple way to demostrate the issue is using:
>
> dbench4 -c /usr/share/dbench4/client.txt -t 10 -D /mnt 1
>
> on ext4 filesystem on plain SATA driver (mounted with barrier=0 to make
> difference more visible). When all processes are in the root cgroup,
> reported throughput is 153.132 MB/sec. When dbench process gets its own
> blkio cgroup, reported throughput drops to 26.1006 MB/sec.
>
> Fix the problem by making check in cfq_should_preempt() more benevolent
> and allow preemption by ancestor cgroup. This improves the throughput
> reported by dbench4 to 48.9106 MB/sec.
>
> Signed-off-by: Jan Kara <jack@suse.com>
Acked-by: Tejun Heo <tj@kernel.org>
Thanks.
--
tejun
next prev parent reply other threads:[~2016-01-08 18:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 15:28 [PATCH 0/5 v2] SYNC_NOIDLE preemption for ancestor cgroups Jan Kara
2016-01-07 15:28 ` [PATCH 1/5] cfq-iosched: Don't group_idle if cfqq has big thinktime Jan Kara
2016-01-08 16:58 ` Tejun Heo
2016-01-11 15:40 ` Jan Kara
2016-01-07 15:28 ` [PATCH 2/5] cfq-iosched: Reorder checks in cfq_should_preempt() Jan Kara
2016-01-08 16:59 ` Tejun Heo
2016-01-07 15:28 ` [PATCH 3/5] cfq-iosched: Allow sync noidle workloads to preempt each other Jan Kara
2016-01-08 18:13 ` Tejun Heo
2016-01-07 15:28 ` [PATCH 4/5] cgroup: Export cgroup_is_descendant() Jan Kara
2016-01-08 18:15 ` Tejun Heo
2016-01-07 15:28 ` [PATCH 5/5] cfq-iosched: Allow parent cgroup to preempt its child Jan Kara
2016-01-08 18:17 ` Tejun Heo [this message]
2016-01-12 15:24 [PATCH 0/5 v3] SYNC_NOIDLE preemption for ancestor cgroups Jan Kara
2016-01-12 15:24 ` [PATCH 5/5] cfq-iosched: Allow parent cgroup to preempt its child Jan Kara
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=20160108181748.GY1898@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=axboe@kernel.dk \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=jmoyer@redhat.com \
--cc=linux-kernel@vger.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
Powered by JetHome