I'd like to propose a discussion topic: IO-less Dirty Throttling Considered Harmful... to isolation and cgroup IO schedulers in general. The disk scheduler is knocked out of the picture unless it can see the IO generated by each group above it. The world of memcg-aware writeback stacked on top of block-cgroups is a complicated one. Throttling in balance_dirty_pages() will likely be a non-starter for current users of group-aware CFQ. I'd like a discussion that covers the system-wide view of: memory -> memcg groups -> block cgroups -> multiple block devices Chad On Mon, Mar 28, 2011 at 9:36 PM, James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx> wrote: > Hi All, > > Since LSF is less than a week away, the programme committee put together > a just in time preliminary agenda for LSF. As you can see there is > still plenty of empty space, which you can make suggestions (to this > list with appropriate general list cc's) for filling: > > https://spreadsheets.google.com/pub?hl=en&hl=en&key=0AiQMl7GcVa7OdFdNQzM5UDRXUnVEbHlYVmZUVHQ2amc&output=html > > If you don't make suggestions, the programme committee will feel > empowered to make arbitrary assignments based on your topic and attendee > email requests ... > > We're still not quite sure what rooms we will have at the Kabuki, but > we'll add them to the spreadsheet when we know (they should be close to > each other). > > The spreadsheet above also gives contact information for all the > attendees and the programme committee. > > Yours, > > James Bottomley > on behalf of LSF/MM Programme Committee > > > _______________________________________________ > Lsf mailing list > Lsf@xxxxxxxxxxxxxxxxxxxxxxxxxx > https://lists.linux-foundation.org/mailman/listinfo/lsf > -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html