On Wed, Jun 24, 2009 at 12:57:40PM +0000, Mike Ramsey wrote: > Bron Gondwana <brong <at> fastmail.fm> writes: > > Meaning that nobody can turn off the write cache in linux without deep kernel > > hackery. > > I would say this differently. "Meaning that nobody can turn off the write cache > in linux without applying the known fixes to libata." Depending on the environment you're in, building a non-default kernel can be tricky. > > Sounds to me like they are benchmarking the real world rather than trying to > favour btrfs by making changes > > that are unlikely to be viable for anyone trying to run it in production. > I.e. they're benchmarking reality. > > Real world is running kernel software that is compatible with the unit under > test. Benchmarking Butters with a broken kernel is not real world; it's unfair. Well, yeah. The world's full of unfair stuff. I would find this valuable information to have if I had a kernel of that vintage. > > Sure there are ways that btrfs performance could be improved, but they're not > realistically available to > > mortals selecting "use btrfs for /home" in their Ubuntu "Bleeding-Edge Badger" > release. > > Butters is experimental. Currently, it should only be used under adult > supervision. I am looking forward to the day that Butters can be used by > novices when they click http://www.ubuntu.com/products/GetUbuntu/download Yeah, that would be nice. I still use reiser3 in locations where I need a good all-round filesystem. Bron ( who probably should get a current kernel again - but the .30rcs were causing fun and games with my soundcard and I didn't have time to go debuggerising them ) -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
