[Gluster-devel] regarding write-behind default values for o-direct & flush behind

[Raghavendra Gowdappa]

----- Original Message -----
> From: "Pranith Kumar Karampuri" <pkarampu at redhat.com>
> To: "Gluster Devel" <gluster-devel at gluster.org>, "Raghavendra Gowdappa" <rgowdapp at redhat.com>
> Cc: "Krutika Dhananjay" <kdhananj at redhat.com>
> 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
>