From: Jens Axboe <axboe@kernel.dk>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: Vivek Goyal <vgoyal@redhat.com>,
linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] blkio-throttle: Avoid calling blkiocg_lookup_group() for root group
Date: Mon, 31 Jan 2011 20:24:00 +0100 [thread overview]
Message-ID: <4D470C50.6010701@kernel.dk> (raw)
In-Reply-To: <x49ei7sq3qe.fsf@segfault.boston.devel.redhat.com>
On 2011-01-31 20:20, Jeff Moyer wrote:
> Vivek Goyal <vgoyal@redhat.com> writes:
>
>> On Mon, Jan 17, 2011 at 04:56:06PM -0500, Vivek Goyal wrote:
>>> o Jeff Moyer was doing some testing on a RAM backed disk and
>>> blkiocg_lookup_group() showed up high overhead after memcpy(). Similarly
>>> somebody else reported that blkiocg_lookup_group() is eating 6% extra
>>> cpu. Though looking at the code I can't think why the overhead of
>>> this function is so high. One thing is that it is called with very high
>>> frequency (once for every IO).
>>>
>>> o For lot of folks blkio controller will be compiled in but they might
>>> not have actually created cgroups. Hence optimize the case of root
>>> cgroup where we can avoid calling blkiocg_lookup_group() if IO is happening
>>> in root group (common case).
>>>
>>> Reported-by: Jeff Moyer <jmoyer@redhat.com>
>>> Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
>>
>> Hi Jens,
>>
>> Do you have any concerns regarding this patch?
>
> Acked-by: Jeff Moyer <jmoyer@redhat.com>
>
> Jens, this is a pretty easy performance regression fixup. I think it
> should be pulled in sooner rather than later. We've also witnessed this
> slowdown on big performance testing rigs, so it's not just a ramdisk
> issue.
Yep, will fold it into 2.6.38, thanks!
--
Jens Axboe
next prev parent reply other threads:[~2011-01-31 19:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 21:56 [PATCH] blkio-throttle: Avoid calling blkiocg_lookup_group() for root group Vivek Goyal
2011-01-17 22:00 ` Jeff Moyer
2011-01-26 18:57 ` Vivek Goyal
2011-01-31 19:20 ` Jeff Moyer
2011-01-31 19:24 ` Jens Axboe [this message]
2011-01-31 19:25 ` Jens Axboe
2011-01-31 19:30 ` Jeff Moyer
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=4D470C50.6010701@kernel.dk \
--to=axboe@kernel.dk \
--cc=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@redhat.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