From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Mon, 24 Aug 2015 00:53:24 -0700 From: Christoph Hellwig To: Artem Bityutskiy Cc: Brian Norris , Richard Weinberger , Dongsheng Yang , linux-mtd@lists.infradead.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 2/2] ubifs: Allow O_DIRECT Message-ID: <20150824075324.GA28336@infradead.org> References: <1440016553-26481-1-git-send-email-richard@nod.at> <1440016553-26481-2-git-send-email-richard@nod.at> <55D542C5.6040500@cn.fujitsu.com> <1440070300.31419.202.camel@gmail.com> <55D5BC92.8050903@nod.at> <20150820204933.GG74600@google.com> <1440400405.15510.29.camel@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1440400405.15510.29.camel@gmail.com> List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, Aug 24, 2015 at 10:13:25AM +0300, Artem Bityutskiy wrote: > 1. we are the only FS erroring out on O_DIRECT > 2. other file-systems not supporting direct IO just fake it There are lots of file systems not supporting O_DIRECT, but ubifs might be the most common one. Given that O_DIRECT implementations aren't hard, so what's holding back a real implementation?