> > Cc: linux-kernel@vger.kernel.org; linux-f2fs-de...@lists.sourceforge.net
> > Subject: Re: [f2fs-dev] [PATCH] f2fs: introduce a new direct_IO write path
> >
> > Change log from v1:
> > o fix NOSPC error handling
> >
> > >From b8511a74fe98b67247a9feeed
ect: Re: [f2fs-dev] [PATCH] f2fs: introduce a new direct_IO write path
>
> Change log from v1:
> o fix NOSPC error handling
>
> >From b8511a74fe98b67247a9feeed58441e8f5ffd705 Mon Sep 17 00:00:00 2001
> From: Jaegeuk Kim
> Date: Mon, 16 Dec 2013 19:04:05 +0900
> Sub
s: introduce a new direct_IO write path
>
> Change log from v1:
> o fix NOSPC error handling
>
> >From b8511a74fe98b67247a9feeed58441e8f5ffd705 Mon Sep 17 00:00:00 2001
> From: Jaegeuk Kim
> Date: Mon, 16 Dec 2013 19:04:05 +0900
> Subject: [PATCH] f2fs: introduc
Change log from v1:
o fix NOSPC error handling
>From b8511a74fe98b67247a9feeed58441e8f5ffd705 Mon Sep 17 00:00:00 2001
From: Jaegeuk Kim
Date: Mon, 16 Dec 2013 19:04:05 +0900
Subject: [PATCH] f2fs: introduce a new direct_IO write path
Cc: linux-fsde...@vger.kernel.org, linux-ker
Previously, f2fs doesn't support direct IOs with high performance which throws
every write requests to the buffered write path, resulting in highly performance
degradation due to memory opeations like copy_from_user.
This patch introduces a new direct IO path in which every write requests are
proc
5 matches
Mail list logo