On Wed, Sep 20, 2017 at 7:06 AM, Kent Overstreet <kent.overstreet@xxxxxxxxx> wrote: > The main thing to be careful about is anything you do that increases scanning > for dirty data has the potential to cause problems by starving foreground writes > via the writeback lock. > > If you or others are going to be working on this code, trying to improve that > locking would probably be very worthwhile... Kent-- This is a very good point. Hopefully the approach I've got where at most the work is doubled (and happens less frequently) isn't too bad on this scale. I will look at making that locking more granular, too, though. :D Thanks, Mike -- To unsubscribe from this list: send the line "unsubscribe linux-bcache" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
