From: Chao Yu <chao2.yu@samsung.com>
To: 'Jaegeuk Kim' <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH 1/2] f2fs: reorganize __f2fs_add_link
Date: Tue, 28 Jul 2015 18:26:25 +0800 [thread overview]
Message-ID: <00e401d0c91f$f301b950$d9052bf0$@samsung.com> (raw)
In-Reply-To: <20150724161117.GA31061@jaegeuk-mac02.hsd1.ca.comcast.net>
Hi Jaegeuk,
> -----Original Message-----
> From: Jaegeuk Kim [mailto:jaegeuk@kernel.org]
> Sent: Saturday, July 25, 2015 12:11 AM
> To: Chao Yu
> Cc: linux-f2fs-devel@lists.sourceforge.net; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH 1/2] f2fs: reorganize __f2fs_add_link
>
> Hi Chao,
>
> BTW, isn't there any problem on update_inode/mark_inode_dirty stuffs?
Any problem here?
> And, is there a hole to write uncompleted node pages unnecessarily?
>
Yes, the hole can be filled.
> > Let me think about this for a while.
> > I think two patches are clean-ups with a little bit big changes.
> > Currently, we've touched many parts including extent_cache, so I need to focus
> > on stabilizing them first.
> > After then, I'd like to dig two clean-up patches. Ok?
It's OK. :)
Thanks,
------------------------------------------------------------------------------
prev parent reply other threads:[~2015-07-28 10:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 10:21 [PATCH 1/2] f2fs: reorganize __f2fs_add_link Chao Yu
2015-07-23 18:15 ` Jaegeuk Kim
2015-07-24 10:31 ` Chao Yu
2015-07-24 15:52 ` Jaegeuk Kim
2015-07-24 16:11 ` Jaegeuk Kim
2015-07-28 10:26 ` 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='00e401d0c91f$f301b950$d9052bf0$@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).