From: Jaegeuk Kim <jaegeuk@kernel.org>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Cc: Jaegeuk Kim <jaegeuk@kernel.org>
Subject: [PATCH 3/3] f2fs crypto: preallocate BIO_MAX_PAGES for writeback
Date: Thu, 21 May 2015 17:40:25 -0700 [thread overview]
Message-ID: <1432255225-76792-3-git-send-email-jaegeuk@kernel.org> (raw)
In-Reply-To: <1432255225-76792-1-git-send-email-jaegeuk@kernel.org>
This patch changes the number of preallocated pages to BIO_MAX_PAGES to prepare
writeback encryption.
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
---
fs/f2fs/crypto.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/f2fs/crypto.c b/fs/f2fs/crypto.c
index 2ceee68..cfe5a04 100644
--- a/fs/f2fs/crypto.c
+++ b/fs/f2fs/crypto.c
@@ -48,7 +48,7 @@
/* Encryption added and removed here! (L: */
-static unsigned int num_prealloc_crypto_pages = 32;
+static unsigned int num_prealloc_crypto_pages = BIO_MAX_PAGES;
static unsigned int num_prealloc_crypto_ctxs = 128;
module_param(num_prealloc_crypto_pages, uint, 0444);
--
2.1.1
prev parent reply other threads:[~2015-05-22 0:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 0:40 [PATCH 1/3] f2fs crypto: use per-inode tfm structure Jaegeuk Kim
2015-05-22 0:40 ` [PATCH 2/3] f2fs crypto: use bounce pages from mempool first Jaegeuk Kim
2015-05-25 10:00 ` [f2fs-dev] " Chao Yu
2015-05-27 19:09 ` Jaegeuk Kim
2015-05-29 2:45 ` Chao Yu
2015-05-25 19:55 ` Theodore Ts'o
2015-05-27 21:18 ` Jaegeuk Kim
2015-05-28 18:18 ` Theodore Ts'o
2015-05-29 19:10 ` nick
2015-05-28 4:21 ` [PATCH 2/3 v2] " Jaegeuk Kim
2015-05-22 0:40 ` Jaegeuk Kim [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1432255225-76792-3-git-send-email-jaegeuk@kernel.org \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).