Re: [PATCH 0/12] Per-bdi writeback flusher threads v7

[Damien Wyart]

Hello,

I have been playing with v7 since your sending and after a white (short
on laptop, longer on desktop, a few hours), writeback doesn't seem to
work anymore. Manual call to sync hangs (process in D state) and Dirty
value in meminfo gets growing. As previous versions had been heavily
tested, I guess there is some regression in v7.


Best

Damien Wyart

> Here's the 7th version of the writeback patches. Changes since
> v5/v6:

> - Move the sync_supers() to the global bdi_forker_task() thread, so we
>   don't writeback the supers from all the bdi kupdated() tasks.
> - Make bdi_start_writeback() and bdi_writeback_all() be sync when called
>   with WB_SYNC_ALL only.
> - Shuffle some more things around to make a cleaner series. The sync vs
>   async nature of bdi_writeback_all() and bdi_start_writeback() isn't
>   consistent through the series, but otherwise things should be sane.

> I'd appreciate if Richard and Yanmin could re-run testing with this,
> just to make sure that things are sane. For ease of patching, I've
> put the full diff here:

>   http://kernel.dk/writeback-v7.patch

> and also stored this in a writeback-v7 branch that will not change,
> you can pull that into Linus tree from here:

>   git://git.kernel.dk/linux-2.6-block.git writeback-v7


-- 
Damien Wyart
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/