From: Chao Yu <chao2.yu@samsung.com>
To: 'Jaegeuk Kim' <jaegeuk@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: RE: [PATCH 2/7] f2fs: do in batches truncation in truncate_hole
Date: Thu, 17 Sep 2015 20:20:47 +0800 [thread overview]
Message-ID: <009a01d0f143$5f5bf7f0$1e13e7d0$@samsung.com> (raw)
In-Reply-To: <20150916180112.GB99097@jaegeuk-mac02.mot.com>
> -----Original Message-----
> From: Jaegeuk Kim [mailto:jaegeuk@kernel.org]
> Sent: Thursday, September 17, 2015 2:01 AM
> To: Chao Yu
> Cc: linux-f2fs-devel@lists.sourceforge.net; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH 2/7] f2fs: do in batches truncation in truncate_hole
>
> Hi Chao,
>
> How about changing the original patch slightly like below?
>
> o don't have to use index variable
> o should not skip the entire dnode indices, when one of them is -ENOENT
Agree, thanks for your review! :)
Thanks,
prev parent reply other threads:[~2015-09-17 12:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 6:38 [PATCH 2/7] f2fs: do in batches truncation in truncate_hole Chao Yu
2015-09-16 18:01 ` Jaegeuk Kim
2015-09-17 12:20 ` Chao Yu [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='009a01d0f143$5f5bf7f0$1e13e7d0$@samsung.com' \
--to=chao2.yu@samsung.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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).