----- Original Message ----- > From: "Pranith Kumar Karampuri" <pkarampu@xxxxxxxxxx> > To: "Gluster Devel" <gluster-devel@xxxxxxxxxxx>, "Raghavendra Gowdappa" <rgowdapp@xxxxxxxxxx> > Cc: "Krutika Dhananjay" <kdhananj@xxxxxxxxxx> > Sent: Wednesday, March 16, 2016 4:16:15 PM > Subject: regarding write-behind default values for o-direct & flush behind > > hi Raghavendra, > Krutika showed me this code in write-behind about not honoring > O_DIRECT. 1) Is there any reason why we do flush-behind by default and > 2) Not honor O_DIRECT in write-behind by default (strict-O_DIRECT option)? I think both are for performance gains. If someone wants consistency with performance trade-offs, they should explicitly choose it. Also, please note that irrespective of flush-behind values, write-behind waits till all the previous writes are complete before unwinding flush call. > > Pranith > _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
