From: Jens Axboe <axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
To: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: ctalbott-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org,
rni-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org,
containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: Re: [PATCHSET] block: fixes for long standing issues
Date: Fri, 20 Apr 2012 10:10:31 +0200 [thread overview]
Message-ID: <20120420081031.GI7505@kernel.dk> (raw)
In-Reply-To: <1334878164-24788-1-git-send-email-tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
On Thu, Apr 19 2012, Tejun Heo wrote:
> Hello,
>
> This patchset fixes two long standing issues and one relatively new
> css ref leak.
>
> a. elvpriv alloc failure, including ioc and icq failures, fails
> request allocation. As those aren't mempool backed and may fail
> indefinitely, this can lead to deadlock under memory pressure.
>
> b. blkgs don't have proper indexing. With enough number of
> request_queues and blk-throttle enabled, block layer can spend
> considerable amount of cpu cycles walking the same list over and
> over again.
>
> c. __blkg_lookup_create() was leaking a css ref on failure path.
>
> This patchset contains the following four patches.
>
> 0001-block-collapse-blk_alloc_request-into-get_request.patch
> 0002-block-fix-elvpriv-allocation-failure-handling.patch
> 0003-blkcg-fix-blkcg-css-ref-leak-in-__blkg_lookup_create.patch
> 0004-blkcg-use-radix-tree-to-index-blkgs-from-blkcg.patch
>
> 0001-0002 fix #a. 0003 fixes #c. 0004 fixes #b.
>
> This patchset is on top of
>
> block/for-3.5/core 5bc4afb1ec "blkcg: drop BLKCG_STAT_{PRIV|POL|OFF} macros"
> + [1] [PATCHSET] block: per-queue policy activation, take#2
> + [2] [PATCHSET] block: cosmetic updates to blkcg API
Applied, thanks Tejun.
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <axboe@kernel.dk>
To: Tejun Heo <tj@kernel.org>
Cc: vgoyal@redhat.com, ctalbott@google.com, rni@google.com,
cgroups@vger.kernel.org, containers@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHSET] block: fixes for long standing issues
Date: Fri, 20 Apr 2012 10:10:31 +0200 [thread overview]
Message-ID: <20120420081031.GI7505@kernel.dk> (raw)
In-Reply-To: <1334878164-24788-1-git-send-email-tj@kernel.org>
On Thu, Apr 19 2012, Tejun Heo wrote:
> Hello,
>
> This patchset fixes two long standing issues and one relatively new
> css ref leak.
>
> a. elvpriv alloc failure, including ioc and icq failures, fails
> request allocation. As those aren't mempool backed and may fail
> indefinitely, this can lead to deadlock under memory pressure.
>
> b. blkgs don't have proper indexing. With enough number of
> request_queues and blk-throttle enabled, block layer can spend
> considerable amount of cpu cycles walking the same list over and
> over again.
>
> c. __blkg_lookup_create() was leaking a css ref on failure path.
>
> This patchset contains the following four patches.
>
> 0001-block-collapse-blk_alloc_request-into-get_request.patch
> 0002-block-fix-elvpriv-allocation-failure-handling.patch
> 0003-blkcg-fix-blkcg-css-ref-leak-in-__blkg_lookup_create.patch
> 0004-blkcg-use-radix-tree-to-index-blkgs-from-blkcg.patch
>
> 0001-0002 fix #a. 0003 fixes #c. 0004 fixes #b.
>
> This patchset is on top of
>
> block/for-3.5/core 5bc4afb1ec "blkcg: drop BLKCG_STAT_{PRIV|POL|OFF} macros"
> + [1] [PATCHSET] block: per-queue policy activation, take#2
> + [2] [PATCHSET] block: cosmetic updates to blkcg API
Applied, thanks Tejun.
--
Jens Axboe
next prev parent reply other threads:[~2012-04-20 8:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 23:29 [PATCHSET] block: fixes for long standing issues Tejun Heo
2012-04-19 23:29 ` Tejun Heo
[not found] ` <1334878164-24788-1-git-send-email-tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2012-04-19 23:29 ` [PATCH 1/4] block: collapse blk_alloc_request() into get_request() Tejun Heo
2012-04-19 23:29 ` Tejun Heo
2012-04-19 23:29 ` Tejun Heo
2012-04-19 23:29 ` [PATCH 2/4] block: fix elvpriv allocation failure handling Tejun Heo
2012-04-19 23:29 ` Tejun Heo
2012-04-19 23:29 ` Tejun Heo
2012-04-19 23:29 ` [PATCH 3/4] blkcg: fix blkcg->css ref leak in __blkg_lookup_create() Tejun Heo
2012-04-19 23:29 ` Tejun Heo
2012-04-19 23:29 ` [PATCH 4/4] blkcg: use radix tree to index blkgs from blkcg Tejun Heo
2012-04-20 8:10 ` Jens Axboe [this message]
2012-04-20 8:10 ` [PATCHSET] block: fixes for long standing issues Jens Axboe
2012-04-19 23:29 ` [PATCH 4/4] blkcg: use radix tree to index blkgs from blkcg Tejun Heo
[not found] ` <1334878164-24788-5-git-send-email-tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2012-04-20 17:26 ` Vivek Goyal
2012-04-20 17:26 ` Vivek Goyal
2012-04-20 17:26 ` Vivek Goyal
-- strict thread matches above, loose matches on Subject: below --
2012-04-19 23:29 [PATCHSET] block: fixes for long standing issues Tejun Heo
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=20120420081031.GI7505@kernel.dk \
--to=axboe-tswwg44o7x1aa/9udqfwiw@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=ctalbott-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rni-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.