All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Christopherson <jon@jons.org>
To: Tejun Heo <tj@kernel.org>, Jens Axboe <axboe@kernel.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2 block/for-linus] writeback: don't drain bdi_writeback_congested on bdi destruction
Date: Wed, 1 Jul 2015 22:02:14 -0500	[thread overview]
Message-ID: <5594A9B6.2050100@jons.org> (raw)
In-Reply-To: <20150702005337.GB26440@mtj.duckdns.org>



On 07/01/2015 07:53 PM, Tejun Heo wrote:
> 52ebea749aae ("writeback: make backing_dev_info host cgroup-specific
> bdi_writebacks") made bdi (backing_dev_info) host per-cgroup wb's
> (bdi_writeback's).  As the congested state needs to be per-wb and
> referenced from blkcg side and multiple wbs, the patch made all
> non-root cong's (bdi_writeback_congested's) reference counted and
> indexed on bdi.
>
<snip>

Thanks Tejun,

     I have applied your patches and no longer see the behavior 
mentioned in the bug report. All is well!

-Jon

  reply	other threads:[~2015-07-02  3:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-02  0:52 [PATCH 1/2 block/for-linus] writeback: don't embed root bdi_writeback_congested in bdi_writeback Tejun Heo
2015-07-02  0:53 ` [PATCH 2/2 block/for-linus] writeback: don't drain bdi_writeback_congested on bdi destruction Tejun Heo
2015-07-02  3:02   ` Jon Christopherson [this message]
     [not found]     ` <5594AD98.4050402@jons.org>
2015-07-02 13:21       ` [PATCH] tools/perf, rbtree: Add RCU wrappers to make rbtree.h usable in user-space Tejun Heo
2015-07-02 20:51         ` Rusty Russell
2015-07-03  7:14           ` Peter Zijlstra
2015-07-03 10:00             ` Jon Christopherson
2015-07-04 16:15             ` Arnaldo Carvalho de Melo
2015-07-06 10:57               ` Peter Zijlstra
2015-07-02 14:04     ` [PATCH 2/2 block/for-linus] writeback: don't drain bdi_writeback_congested on bdi destruction Jens Axboe

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=5594A9B6.2050100@jons.org \
    --to=jon@jons.org \
    --cc=axboe@kernel.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@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 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.