From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <yuchao0@huawei.com>
Cc: Chao Yu <chao@kernel.org>,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] f2fs: fix to redirty page if fail to gc data page
Date: Fri, 3 Jun 2016 10:36:54 -0700 [thread overview]
Message-ID: <20160603173654.GA29066@jaegeuk> (raw)
In-Reply-To: <e0ec235d-67ac-751f-a343-f227525fd19b@huawei.com>
On Fri, Jun 03, 2016 at 01:59:15PM +0800, Chao Yu wrote:
...
> >>> Do we have another expectation?
> >>
> >> ENOMEM or EIO?
> >
> > EIO will stop everything.
> > ENOMEM would be better to wait for a while from page reclaim?
>
> Agree, but for ioctl path, IMO, we don't need to let user waiting for ENOMEM
> case looping.
Well, if user wanted to do a synchronous gc, we need that, IMO.
prev parent reply other threads:[~2016-06-03 17:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-21 5:19 [PATCH] f2fs: fix to redirty page if fail to gc data page Chao Yu
2016-05-28 0:54 ` Chao Yu
2016-05-30 2:37 ` Jaegeuk Kim
2016-05-31 6:10 ` Chao Yu
2016-06-03 5:08 ` Jaegeuk Kim
2016-06-03 5:13 ` Chao Yu
2016-06-03 5:17 ` Jaegeuk Kim
2016-06-03 5:59 ` Chao Yu
2016-06-03 17:36 ` 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=20160603173654.GA29066@jaegeuk \
--to=jaegeuk@kernel.org \
--cc=chao@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=yuchao0@huawei.com \
/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).