From: Chao Yu <chao2.yu@samsung.com>
To: "'Jaegeuk Kim'" <jaegeuk@kernel.org>,
"'Changman Lee'" <cm224.lee@samsung.com>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: RE: [f2fs-dev] [PATCH v3 06/10] f2fs: add core functions for rb-tree extent cache
Date: Mon, 16 Feb 2015 16:10:54 +0800 [thread overview]
Message-ID: <006301d049c0$3c6ed7b0$b54c8710$@samsung.com> (raw)
In-Reply-To: <000301d04129$d7546000$85fd2000$@samsung.com>
Ping.
Any comments on this patch now?
> -----Original Message-----
> From: Chao Yu [mailto:chao2.yu@samsung.com]
> Sent: Thursday, February 05, 2015 5:55 PM
> To: Jaegeuk Kim; Changman Lee
> Cc: linux-kernel@vger.kernel.org; linux-f2fs-devel@lists.sourceforge.net
> Subject: [f2fs-dev] [PATCH v3 06/10] f2fs: add core functions for rb-tree extent cache
>
> This patch adds core functions including slab cache init function and
> init/lookup/update/shrink/destroy function for rb-tree based extent cache.
>
> Thank Jaegeuk Kim and Changman Lee as they gave much suggestion about detail
> design and implementation of extent cache.
>
> Todo:
> * register rb-based extent cache shrink with mm shrink interface.
>
> v2:
> o move set_extent_info and __is_{extent,back,front}_mergeable into f2fs.h.
> o introduce __{attach,detach}_extent_node for code readability.
> o add cond_resched() when fail to invoke kmem_cache_alloc/radix_tree_insert.
> o fix some coding style and typo issues.
>
> v3:
> o fix oops due to using an unassigned pointer.
> o use list_del to remove extent node in shrink list.
next prev parent reply other threads:[~2015-02-16 8:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 9:54 [PATCH v3 06/10] f2fs: add core functions for rb-tree extent cache Chao Yu
2015-02-16 8:10 ` Chao Yu [this message]
2015-02-18 6:32 ` [f2fs-dev] " 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='006301d049c0$3c6ed7b0$b54c8710$@samsung.com' \
--to=chao2.yu@samsung.com \
--cc=cm224.lee@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).