> > actually a global dirty_ratio causes interference between devices which > > should otherwise not block each other... > > > > if you set up a "dd if=/dev/zero of=/dev/sdb bs=1M" it shouldn't affect > > write performance on sda -- but it does... because the dd basically > > dirties all of the "dirty_background_ratio" pages and then any task > > writing to sda has to block in the foreground... (i've had this happen in > > practice -- my hack fix is oflag=direct on the dd... but the problem still > > exists.) > > yeah. Plus your heavy-dd-to-/dev/sda tends to block light-writers to > /dev/sda in perhaps disproportionate ways. > > This is on my list of things to look at. Hah.
It really exists in the wild on both large memory and storage machines. I hope we don't have to patch Samba on every release to add POSIX fadvise calls in order to have a more polite VM. A 'cfq' for write generators from vm to devices would be nice if it can auto probe the device write speed so we don't have to use knobs. Just let the kernel figure out what are the best values to the algorithms would be the ideal world. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/