Re: [f2fs-dev] [PATCH 2/3] f2fs crypto: use bounce pages from mempool first

2015-05-29 Thread nick
On 2015-05-28 02:18 PM, Theodore Ts'o wrote: > On Wed, May 27, 2015 at 02:18:54PM -0700, Jaegeuk Kim wrote: >> The problem that I'd like to address here is to reduce the call counts of >> allocating and freeing a number of pages in pairs. >> >> When I conduct xfstests/224 under 1GB DRAM, I've see

Re: [f2fs-dev] [PATCH 2/3] f2fs crypto: use bounce pages from mempool first

2015-05-28 Thread Chao Yu
dev] [PATCH 2/3] f2fs crypto: use bounce pages from > mempool first > > Hi Chao, > > On Mon, May 25, 2015 at 06:00:47PM +0800, Chao Yu wrote: > > Hi Jaegeuk, > > [snip] > > > > Using alloc_page(GFP_NOFS | __GFP_WAIT) to avoid failure? > > #define GFP

Re: [f2fs-dev] [PATCH 2/3] f2fs crypto: use bounce pages from mempool first

2015-05-28 Thread Theodore Ts'o
On Wed, May 27, 2015 at 02:18:54PM -0700, Jaegeuk Kim wrote: > The problem that I'd like to address here is to reduce the call counts of > allocating and freeing a number of pages in pairs. > > When I conduct xfstests/224 under 1GB DRAM, I've seen triggering several oom > killers, and in that mome

Re: [f2fs-dev] [PATCH 2/3] f2fs crypto: use bounce pages from mempool first

2015-05-27 Thread Jaegeuk Kim
On Mon, May 25, 2015 at 03:55:51PM -0400, Theodore Ts'o wrote: > On Thu, May 21, 2015 at 05:40:24PM -0700, Jaegeuk Kim wrote: > > If a lot of write streams are triggered, alloc_page and __free_page are > > costly called, resulting in high memory pressure. > > > > In order to avoid that, let's reus

Re: [f2fs-dev] [PATCH 2/3] f2fs crypto: use bounce pages from mempool first

2015-05-27 Thread Jaegeuk Kim
rnel.org; > > linux-f2fs-devel@lists.sourceforge.net > > Cc: Jaegeuk Kim > > Subject: [f2fs-dev] [PATCH 2/3] f2fs crypto: use bounce pages from mempool > > first > > > > If a lot of write streams are triggered, alloc_page and __free_page are > > costly ca

Re: [f2fs-dev] [PATCH 2/3] f2fs crypto: use bounce pages from mempool first

2015-05-25 Thread Theodore Ts'o
On Thu, May 21, 2015 at 05:40:24PM -0700, Jaegeuk Kim wrote: > If a lot of write streams are triggered, alloc_page and __free_page are > costly called, resulting in high memory pressure. > > In order to avoid that, let's reuse mempool pages for writeback pages. The reason why the mempool pages wa

Re: [f2fs-dev] [PATCH 2/3] f2fs crypto: use bounce pages from mempool first

2015-05-25 Thread Chao Yu
Hi Jaegeuk, > -Original Message- > From: Jaegeuk Kim [mailto:jaeg...@kernel.org] > Sent: Friday, May 22, 2015 8:40 AM > To: linux-ker...@vger.kernel.org; linux-fsde...@vger.kernel.org; > linux-f2fs-devel@lists.sourceforge.net > Cc: Jaegeuk Kim > Subject: [f2fs-dev] [P

[f2fs-dev] [PATCH 2/3] f2fs crypto: use bounce pages from mempool first

2015-05-21 Thread Jaegeuk Kim
If a lot of write streams are triggered, alloc_page and __free_page are costly called, resulting in high memory pressure. In order to avoid that, let's reuse mempool pages for writeback pages. Signed-off-by: Jaegeuk Kim --- fs/f2fs/crypto.c | 16 1 file changed, 4 insertions(+)