Re: [PATCH] Fix queueing work if !bdi_cap_writeback_dirty()

[Jan Kara]

On Mon 17-09-12 18:39:05, OGAWA Hirofumi wrote:
> Jan Kara <jack@xxxxxxx> writes:
> 
> >> I think you know how to solve it though. You can add the periodic flush
> >> in own task. And you can check bdi->dirty_exceeded in any handlers.
> >   Sure, you can have your private thread. That is possible but you will
> > have to duplicate flusher logic and you will still get odd behavior e.g.
> > when your filesystem is on one partition and another filesystem is on a
> > different partition of the same disk.
> 
> Right. But it is what current FSes are doing more or less.
  It's not. Page writeback is respected by all filesystems in most cases
AFAIK. Inode writeback is a different issue but that's not so interesting
from mm point of view...

								Honza
-- 
Jan Kara <jack@xxxxxxx>
SUSE Labs, CR
--
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/