From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <chao2.yu@samsung.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH 04/11] f2fs: use radix_tree for ino management
Date: Tue, 29 Jul 2014 05:34:04 -0700 [thread overview]
Message-ID: <20140729123404.GD84378@jaegeuk-mac02> (raw)
In-Reply-To: <008001cfab20$d5e6ce50$81b46af0$@samsung.com>
Got it.
Fixed that.
Thanks,
On Tue, Jul 29, 2014 at 07:32:08PM +0800, Chao Yu wrote:
> Hi,
>
> One comment as following.
>
> > -----Original Message-----
> > From: Jaegeuk Kim [mailto:jaegeuk@kernel.org]
> > Sent: Saturday, July 26, 2014 6:47 AM
> > To: linux-kernel@vger.kernel.org; linux-fsdevel@vger.kernel.org;
> > linux-f2fs-devel@lists.sourceforge.net
> > Cc: Jaegeuk Kim
> > Subject: [f2fs-dev] [PATCH 04/11] f2fs: use radix_tree for ino management
> >
> > For better ino management, this patch replaces the data structure from list
> > to radix tree.
> >
> > Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
>
> Reviewed-by: Chao Yu <chao2.yu@samsung.com>
>
> > ---
> > fs/f2fs/checkpoint.c | 48 ++++++++++++++++++++++++++----------------------
> > fs/f2fs/f2fs.h | 1 +
> > 2 files changed, 27 insertions(+), 22 deletions(-)
> >
> > diff --git a/fs/f2fs/checkpoint.c b/fs/f2fs/checkpoint.c
> > index f93d154..d35094a 100644
> > --- a/fs/f2fs/checkpoint.c
> > +++ b/fs/f2fs/checkpoint.c
> > @@ -284,24 +284,26 @@ const struct address_space_operations f2fs_meta_aops = {
> >
> > static void __add_ino_entry(struct f2fs_sb_info *sbi, nid_t ino, int type)
> > {
> > - struct ino_entry *new, *e;
> > -
> > - new = f2fs_kmem_cache_alloc(ino_entry_slab, GFP_ATOMIC);
> > - new->ino = ino;
> > -
> > + struct ino_entry *e;
> > +retry:
> > spin_lock(&sbi->ino_lock[type]);
> > - list_for_each_entry(e, &sbi->ino_list[type], list) {
> > - if (e->ino == ino) {
> > +
> > + e = radix_tree_lookup(&sbi->ino_root[type], ino);
> > + if (!e) {
> > + e = kmem_cache_alloc(ino_entry_slab, GFP_ATOMIC);
> > + if (!e) {
> > spin_unlock(&sbi->ino_lock[type]);
> > - kmem_cache_free(ino_entry_slab, new);
> > - return;
> > + goto retry;
> > }
> > - if (e->ino > ino)
> > - break;
> > - }
> > + if (radix_tree_insert(&sbi->ino_root[type], ino, e)) {
> > + spin_unlock(&sbi->ino_lock[type]);
>
> we should add kmem_cache_free(ino_entry_slab, e) here to avoid memory leak.
>
> > + goto retry;
> > + }
> > + memset(e, 0, sizeof(struct ino_entry));
> > + e->ino = ino;
> >
> > - /* add new entry into list which is sorted by inode number */
> > - list_add_tail(&new->list, &e->list);
> > + list_add_tail(&e->list, &sbi->ino_list[type]);
> > + }
> > spin_unlock(&sbi->ino_lock[type]);
> > }
> >
> > @@ -310,14 +312,15 @@ static void __remove_ino_entry(struct f2fs_sb_info *sbi, nid_t ino, int
> > type)
> > struct ino_entry *e;
> >
> > spin_lock(&sbi->ino_lock[type]);
> > - list_for_each_entry(e, &sbi->ino_list[type], list) {
> > - if (e->ino == ino) {
> > - list_del(&e->list);
> > + e = radix_tree_lookup(&sbi->ino_root[type], ino);
> > + if (e) {
> > + list_del(&e->list);
> > + radix_tree_delete(&sbi->ino_root[type], ino);
> > + if (type == ORPHAN_INO)
> > sbi->n_orphans--;
> > - spin_unlock(&sbi->ino_lock[type]);
> > - kmem_cache_free(ino_entry_slab, e);
> > - return;
> > - }
> > + spin_unlock(&sbi->ino_lock[type]);
> > + kmem_cache_free(ino_entry_slab, e);
> > + return;
> > }
> > spin_unlock(&sbi->ino_lock[type]);
> > }
> > @@ -346,7 +349,7 @@ void release_orphan_inode(struct f2fs_sb_info *sbi)
> >
> > void add_orphan_inode(struct f2fs_sb_info *sbi, nid_t ino)
> > {
> > - /* add new orphan entry into list which is sorted by inode number */
> > + /* add new orphan ino entry into list */
> > __add_ino_entry(sbi, ino, ORPHAN_INO);
> > }
> >
> > @@ -943,6 +946,7 @@ void init_ino_entry_info(struct f2fs_sb_info *sbi)
> > int i;
> >
> > for (i = 0; i < MAX_INO_ENTRY; i++) {
> > + INIT_RADIX_TREE(&sbi->ino_root[i], GFP_ATOMIC);
> > spin_lock_init(&sbi->ino_lock[i]);
> > INIT_LIST_HEAD(&sbi->ino_list[i]);
> > }
> > diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h
> > index b6fa6ec..4454caa 100644
> > --- a/fs/f2fs/f2fs.h
> > +++ b/fs/f2fs/f2fs.h
> > @@ -456,6 +456,7 @@ struct f2fs_sb_info {
> > wait_queue_head_t cp_wait;
> >
> > /* for inode management */
> > + struct radix_tree_root ino_root[MAX_INO_ENTRY]; /* ino entry array */
> > spinlock_t ino_lock[MAX_INO_ENTRY]; /* for ino entry lock */
> > struct list_head ino_list[MAX_INO_ENTRY]; /* inode list head */
> >
> > --
> > 1.8.5.2 (Apple Git-48)
> >
> >
> > ------------------------------------------------------------------------------
> > Want fast and easy access to all the code in your enterprise? Index and
> > search up to 200,000 lines of code with a free copy of Black Duck
> > Code Sight - the same software that powers the world's largest code
> > search on Ohloh, the Black Duck Open Hub! Try it now.
> > http://p.sf.net/sfu/bds
> > _______________________________________________
> > Linux-f2fs-devel mailing list
> > Linux-f2fs-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls.
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
next prev parent reply other threads:[~2014-07-29 12:34 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 22:47 [PATCH 01/11] f2fs: add nobarrier mount option Jaegeuk Kim
2014-07-25 22:47 ` [PATCH 02/11] f2fs: punch the core function for inode management Jaegeuk Kim
2014-07-29 11:29 ` Chao Yu
2014-07-25 22:47 ` [PATCH 03/11] f2fs: add infra for ino management Jaegeuk Kim
2014-07-29 11:30 ` Chao Yu
2014-07-25 22:47 ` [PATCH 04/11] f2fs: use radix_tree " Jaegeuk Kim
2014-07-29 11:32 ` Chao Yu
2014-07-29 12:34 ` Jaegeuk Kim [this message]
2014-07-25 22:47 ` [PATCH 05/11] f2fs: add info of appended or updated data writes Jaegeuk Kim
2014-07-29 11:38 ` Chao Yu
2014-07-25 22:47 ` [PATCH 06/11] f2fs: skip unnecessary data writes during fsync Jaegeuk Kim
2014-07-29 11:39 ` Chao Yu
2014-07-29 12:43 ` Jaegeuk Kim
2014-07-30 11:58 ` Chao Yu
2014-07-25 22:47 ` [PATCH 07/11] f2fs: enable in-place-update for fdatasync Jaegeuk Kim
2014-07-29 0:41 ` Changman Lee
2014-07-29 12:22 ` [f2fs-dev] " Jaegeuk Kim
2014-07-29 23:54 ` Changman Lee
2014-07-30 1:08 ` Jaegeuk Kim
2014-07-30 1:56 ` [f2fs-dev] " Changman Lee
2014-07-30 3:11 ` Jaegeuk Kim
2014-07-30 2:45 ` [f2fs-dev] " Chao Yu
2014-07-30 3:13 ` Jaegeuk Kim
2014-07-30 12:48 ` [f2fs-dev] " Chao Yu
2014-07-25 22:47 ` [PATCH 08/11] f2fs: fix wrong condition for unlikely Jaegeuk Kim
2014-07-30 1:44 ` Chao Yu
2014-07-30 3:18 ` Jaegeuk Kim
2014-07-30 12:58 ` Chao Yu
2014-07-25 22:47 ` [PATCH 09/11] f2fs: test before set/clear bits Jaegeuk Kim
2014-07-25 22:47 ` [PATCH 10/11] f2fs: avoid checkpoint when error was occurred Jaegeuk Kim
2014-07-29 11:41 ` Chao Yu
2014-07-29 13:00 ` Jaegeuk Kim
2014-07-25 22:47 ` [PATCH 11/11] f2fs: avoid retrying wrong recovery routine " Jaegeuk Kim
2014-07-29 13:01 ` [PATCH v2 " Jaegeuk Kim
2014-07-29 11:28 ` [PATCH 01/11] f2fs: add nobarrier mount option Chao Yu
2014-07-29 12:22 ` 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=20140729123404.GD84378@jaegeuk-mac02 \
--to=jaegeuk@kernel.org \
--cc=chao2.yu@samsung.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--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).