From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: <linux-f2fs-devel@lists.sourceforge.net>,
<linux-kernel@vger.kernel.org>, <chao@kernel.org>
Subject: Re: [PATCH v4] f2fs: obsolete free nid list approach
Date: Mon, 18 Dec 2017 19:56:08 +0800 [thread overview]
Message-ID: <efa09a49-3e18-acd3-7deb-de543db5e550@huawei.com> (raw)
In-Reply-To: <20171214192156.GA35234@jaegeuk-macbookpro.roam.corp.google.com>
On 2017/12/15 3:21, Jaegeuk Kim wrote:
> On 12/11, Chao Yu wrote:
>> Hi Jaegeuk,
>>
>> On 2017/12/1 15:36, Jaegeuk Kim wrote:
>>> Hi Chao,
>>>
>>> This is really hard to review and risky a lot to apply it shortly. Do we have a
>>
>> I can understand your concern.
>>
>>> strong reason we have to do this? The original design goal was to minimize
>>> allocation delay which is almost zero for now. Of course, I agreed that there'd
>>
>> I agreed, For nid allocation performance there will be no room to improve since
>> we have already used memory to exchange performance there.
>>
>> After applying this patch, I can encounter slight regression in scenario of
>> continuous file creation.
>>
>> Anyway, goal of this patch is not aiming at performance, instead, it intends to
>> reduce code complexity, and maybe, slightly improving performance of allocation
>> in low-memory environment. So actually, this is a trade-off problem.
>>
>> If we decide to use old approach, I think what can be improved is that if we run
>> out-of-memory, we can switch to nid bitmap searching in alloc_nid rather than
>> preloading free nid entry in build_free_nid whose performance is memory sensitive.
>> Thoughts?
>
> Hmm, in terms of performance, do we really suffer from memory pressure when
> preloading free nids?
Sorry for late reply, I'm on trip now. I guess it will, let me emulate low
memory environment, and do intensive allocation test, will report to you if
there is any progress.
Thanks,
prev parent reply other threads:[~2017-12-18 11:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 11:31 Chao Yu
2017-12-01 7:36 ` Jaegeuk Kim
2017-12-11 9:38 ` Chao Yu
2017-12-14 19:21 ` Jaegeuk Kim
2017-12-18 11:56 ` 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=efa09a49-3e18-acd3-7deb-de543db5e550@huawei.com \
--to=yuchao0@huawei.com \
--cc=chao@kernel.org \
--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
all inboxes | Powered by JetHome®