Prev: writeback: do not lose wake-ups in the forker thread
Next: writeback: add to bdi_list in the forker thread
From: Christoph Hellwig on 18 Jul 2010 03:00
> This patch also removes strange comment about a temporary measure,
> because there is nothing temporary there - many FSes use default
> bdi.

I don't think that's correct. We're not using default_backing_dev_info
for filesystems anymore for various reasons. Look at the spread of
private bdi initializations for all the non-block backed filesystems.

The actual __set_current_state change looks good to me, but shouldn't
have been mixed up with this to start with.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: writeback: do not lose wake-ups in the forker thread
Next: writeback: add to bdi_list in the forker thread