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 <[email protected]>
---
 fs/f2fs/crypto.c | 16 ++++------------
 1 file changed, 4 insertions(+), 12 deletions(-)

diff --git a/fs/f2fs/crypto.c b/fs/f2fs/crypto.c
index 2c7819a..2ceee68 100644
--- a/fs/f2fs/crypto.c
+++ b/fs/f2fs/crypto.c
@@ -408,20 +408,12 @@ struct page *f2fs_encrypt(struct inode *inode,
                return (struct page *)ctx;
 
        /* The encryption operation will require a bounce page. */
-       ciphertext_page = alloc_page(GFP_NOFS);
+       ciphertext_page = mempool_alloc(f2fs_bounce_page_pool, GFP_NOFS);
        if (!ciphertext_page) {
-               /*
-                * This is a potential bottleneck, but at least we'll have
-                * forward progress.
-                */
-               ciphertext_page = mempool_alloc(f2fs_bounce_page_pool,
-                                                       GFP_NOFS);
-               if (WARN_ON_ONCE(!ciphertext_page))
-                       ciphertext_page = mempool_alloc(f2fs_bounce_page_pool,
-                                               GFP_NOFS | __GFP_WAIT);
-               ctx->flags &= ~F2FS_BOUNCE_PAGE_REQUIRES_FREE_ENCRYPT_FL;
-       } else {
+               ciphertext_page = alloc_page(GFP_NOFS);
                ctx->flags |= F2FS_BOUNCE_PAGE_REQUIRES_FREE_ENCRYPT_FL;
+       } else {
+               ctx->flags &= ~F2FS_BOUNCE_PAGE_REQUIRES_FREE_ENCRYPT_FL;
        }
        ctx->flags |= F2FS_WRITE_PATH_FL;
        ctx->w.bounce_page = ciphertext_page;
-- 
2.1.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to