linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Jan Kara <jack@suse.cz>
Cc: axboe@kernel.dk, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCHSET block/for-next] writeback: prepare for cgroup writeback support
Date: Thu, 20 Nov 2014 10:14:56 -0500	[thread overview]
Message-ID: <20141120151456.GE14877@htj.dyndns.org> (raw)
In-Reply-To: <20141120151311.GE2330@quack.suse.cz>

On Thu, Nov 20, 2014 at 04:13:11PM +0100, Jan Kara wrote:
> On Tue 18-11-14 03:37:18, Tejun Heo wrote:
> > Hello,
> > 
> > This patchset contains the following 10 prepatory patches for cgroup
> > writeback support.  None of these patches introduces behavior changes.
> > 
> >  0001-writeback-move-backing_dev_info-state-into-bdi_write.patch
> >  0002-writeback-move-backing_dev_info-bdi_stat-into-bdi_wr.patch
> >  0003-writeback-move-bandwidth-related-fields-from-backing.patch
> >  0004-writeback-move-backing_dev_info-wb_lock-and-worklist.patch
> >  0005-writeback-move-lingering-dirty-IO-lists-transfer-fro.patch
> >  0006-writeback-reorganize-mm-backing-dev.c.patch
> >  0007-writeback-separate-out-include-linux-backing-dev-def.patch
> >  0008-writeback-cosmetic-change-in-account_page_dirtied.patch
> >  0009-writeback-add-gfp-to-wb_init.patch
> >  0010-writeback-move-inode_to_bdi-to-include-linux-backing.patch
> > 
> > 0001-0005 move writeback related fields from bdi (backing_dev_info) to
> > wb (bdi_writeback).  Currently, one bdi embeds one wb and the
> > separation between the two is blurry.  bdi's lock protects wb's fields
> > and fields which are closely related are scattered across the two.
> > These five patches move all fields which are used during writeback
> > into wb.
> > 
> > 0006-0010 are misc prep patches.  They're all rather trivial and each
> > is self-explanatory.
> > 
> > This patchset is on top of the current block/for-next eb494facbee2
> > ("5748c0fce0fd40c87d164d6bee61") and is available in the following git
> > branch.
>   I have no problem with these patches in principle (I'll check individual
> patches in detail) but do you have some higher level design where exactly
> are you going?

Yeah, I'm prepping the actual patchset and it'll go out with high
level description.  Just wanted to send out the prep ones separately
to reduce the patchset to a manageable size.

> PS: I've added CC to linux-fsdevel since there's high chance people miss
> these patches in lkml...

Will do so when posting the actual series.

Thanks.

-- 
tejun

  reply	other threads:[~2014-11-20 15:15 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-18  8:37 [PATCHSET block/for-next] writeback: prepare for cgroup writeback support Tejun Heo
2014-11-18  8:37 ` [PATCH 01/10] writeback: move backing_dev_info->state into bdi_writeback Tejun Heo
2014-11-20 15:27   ` Jan Kara
2014-11-20 15:38     ` Tejun Heo
2014-11-25  1:20     ` NeilBrown
2014-11-18  8:37 ` [PATCH 02/10] writeback: move backing_dev_info->bdi_stat[] " Tejun Heo
2014-11-20 15:31   ` Jan Kara
2014-11-18  8:37 ` [PATCH 03/10] writeback: move bandwidth related fields from backing_dev_info " Tejun Heo
2014-11-20 15:52   ` Jan Kara
2014-11-20 16:01     ` Tejun Heo
2014-11-18  8:37 ` [PATCH 04/10] writeback: move backing_dev_info->wb_lock and ->worklist " Tejun Heo
2014-11-20 16:01   ` Jan Kara
2014-11-20 16:02     ` Tejun Heo
2014-11-20 16:10       ` Jan Kara
2014-11-18  8:37 ` [PATCH 05/10] writeback: move lingering dirty IO lists transfer from bdi_destroy() to wb_exit() Tejun Heo
2014-11-18  8:37 ` [PATCH 06/10] writeback: reorganize mm/backing-dev.c Tejun Heo
2014-11-18  8:37 ` [PATCH 07/10] writeback: separate out include/linux/backing-dev-defs.h Tejun Heo
2014-11-18  8:37 ` [PATCH 08/10] writeback: cosmetic change in account_page_dirtied() Tejun Heo
2014-11-18  8:37 ` [PATCH 09/10] writeback: add @gfp to wb_init() Tejun Heo
2014-11-18  8:37 ` [PATCH 10/10] writeback: move inode_to_bdi() to include/linux/backing-dev.h Tejun Heo
2014-11-20 15:13 ` [PATCHSET block/for-next] writeback: prepare for cgroup writeback support Jan Kara
2014-11-20 15:14   ` Tejun Heo [this message]
2014-11-20 15:44     ` Christoph Hellwig
2014-11-20 16:21       ` 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=20141120151456.GE14877@htj.dyndns.org \
    --to=tj@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).