linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
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: [f2fs-dev] [PATCH] f2fs: reduce lock overhead of extent node releasing
Date: Mon, 06 Jul 2015 20:28:19 +0800	[thread overview]
Message-ID: <004601d0b7e7$5569a660$003cf320$@samsung.com> (raw)
In-Reply-To: <20150704070353.GE15817@jaegeuk-mac02.hsd1.ca.comcast.net>

> -----Original Message-----
> From: Jaegeuk Kim [mailto:jaegeuk@kernel.org]
> Sent: Saturday, July 04, 2015 3:04 PM
> To: Chao Yu
> Cc: linux-kernel@vger.kernel.org; linux-f2fs-devel@lists.sourceforge.net
> Subject: Re: [f2fs-dev] [PATCH] f2fs: reduce lock overhead of extent node releasing
> 
> On Thu, Jul 02, 2015 at 08:40:12PM +0800, Chao Yu wrote:
> > >From e5c6600d01c4462c4e1ee0c70ec1d9319862077d Mon Sep 17 00:00:00 2001
> > From: Chao Yu <chao2.yu@samsung.com>
> > Date: Thu, 2 Jul 2015 18:52:46 +0800
> > Subject: [PATCH] f2fs: reduce lock overhead of extent node releasing
> >
> > Open and close critical section for each extent node when traversing rb-tree
> > results in high overhead of cpu, slows thing down.
> >
> > This patch alternates to batch mode for removing extent nodes under spin lock.
> >
> > Signed-off-by: Chao Yu <chao2.yu@samsung.com>
> > ---
> >  fs/f2fs/data.c | 28 ++++++++++++++++++++--------
> >  1 file changed, 20 insertions(+), 8 deletions(-)
> >
> > diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
> > index 6a706dd..7fb56a0 100644
> > --- a/fs/f2fs/data.c
> > +++ b/fs/f2fs/data.c
> > @@ -441,19 +441,31 @@ static unsigned int __free_extent_tree(struct f2fs_sb_info *sbi,
> >  	struct extent_node *en;
> >  	unsigned int count = et->count;
> >
> > -	node = rb_first(&et->root);
> > -	while (node) {
> > -		next = rb_next(node);
> > -		en = rb_entry(node, struct extent_node, rb_node);
> > +	if (!et->count)
> > +		return 0;
> > +
> > +	/* 1. remove all extent nodes in global lru list */
> > +	if (free_all) {
> > +		spin_lock(&sbi->extent_lock);
> > +		node = rb_first(&et->root);
> > +		while (node) {
> > +			next = rb_next(node);
> > +			en = rb_entry(node, struct extent_node, rb_node);
> >
> > -		if (free_all) {
> > -			spin_lock(&sbi->extent_lock);
> >  			if (!list_empty(&en->list))
> >  				list_del_init(&en->list);
> > -			spin_unlock(&sbi->extent_lock);
> > +			node = next;
> >  		}
> > +		spin_unlock(&sbi->extent_lock);
> > +	}
> > +
> > +	/* 2. release all extent nodes which are not in global lru list */
> 
> Hmm,
> Is there any overhead to traverse the rb_tree twice and 

Yes, it will cost us more time to traverse the rb tree twice, adding one more
shrink list may reduce the overhead.

> any spin_lock delay caused by contention?

Maybe, since our critical region is enlarged, but the overhead of operation
for re-entering the critical region will be decreased as we invoke spin_lock
only one time.

Thanks,

> 
> Thanks,
> 
> > +	node = rb_first(&et->root);
> > +	while (node) {
> > +		next = rb_next(node);
> > +		en = rb_entry(node, struct extent_node, rb_node);
> >
> > -		if (free_all || list_empty(&en->list)) {
> > +		if (list_empty(&en->list)) {
> >  			__detach_extent_node(sbi, et, en);
> >  			kmem_cache_free(extent_node_slab, en);
> >  		}
> > --
> > 2.4.2
> 
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

      reply	other threads:[~2015-07-06 12:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-02 12:40 [PATCH] f2fs: reduce lock overhead of extent node releasing Chao Yu
2015-07-04  7:03 ` Jaegeuk Kim
2015-07-06 12:28   ` 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='004601d0b7e7$5569a660$003cf320$@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).