From: Chao Yu <chao2.yu@samsung.com>
To: 'Jaegeuk Kim' <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: RE: [f2fs-dev] [PATCH 2/3] f2fs crypto: use bounce pages from mempool first
Date: Fri, 29 May 2015 10:45:46 +0800 [thread overview]
Message-ID: <002601d099b9$abafd090$030f71b0$@samsung.com> (raw)
In-Reply-To: <20150527190815.GA91133@jaegeuk-mac02.mot-mobility.com>
Hi Jaegeuk,
> -----Original Message-----
> From: Jaegeuk Kim [mailto:jaegeuk@kernel.org]
> Sent: Thursday, May 28, 2015 3:10 AM
> To: Chao Yu
> Cc: linux-kernel@vger.kernel.org; linux-fsdevel@vger.kernel.org;
> linux-f2fs-devel@lists.sourceforge.net
> Subject: Re: [f2fs-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_NOFS (__GFP_WAIT | __GFP_IO)
That's right, my miss.
Thanks,
next prev parent reply other threads:[~2015-05-29 2:45 UTC|newest]
Thread overview: 13+ 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-22 0:40 ` 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 [this message]
2015-05-25 19:55 ` Theodore Ts'o
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 ` [PATCH 3/3] f2fs crypto: preallocate BIO_MAX_PAGES for writeback Jaegeuk Kim
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='002601d099b9$abafd090$030f71b0$@samsung.com' \
--to=chao2.yu@samsung.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.