Date: Fri, 15 Jan 2016 04:05:01 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 206238] FUSE can't enter to DIRECT_IO mode during file create. Message-ID: <bug-206238-3630-PlmmxLIEoy@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-206238-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-206238-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206238 rmacklem@uoguelph.ca changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rmacklem@uoguelph.ca --- Comment #1 from rmacklem@uoguelph.ca --- Are you referring to cases where the MooseFS fuse file system sets FOPEN_DIRECT_IO in the reply to a fuse open? or Are you referring to processes on FreeBSD that open with O_DIRECT? Btw, if you look at PR#194293, I have a patch there that forces DIRECT_IO for the case of WRONLY opens, so that a small buffered write doesn't get into trouble when the buffer cache code tries to read the entire block in. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-206238-3630-PlmmxLIEoy>