linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <yuchao0@huawei.com>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH] f2fs: no need lock_op in f2fs_write_inline_data
Date: Fri, 24 Feb 2017 18:10:23 -0800	[thread overview]
Message-ID: <20170225021023.GC50867@jaegeuk.local> (raw)
In-Reply-To: <ffdfdb1c-4a33-2d81-7776-2fd001cc85ec@huawei.com>

On 02/25, Chao Yu wrote:
> On 2017/2/25 3:58, Jaegeuk Kim wrote:
> > On 02/24, heyunlei wrote:
> >> Hi Jaegeuk,
> >>
> >> 	Can you explain more about this? Besides, how about inplace update?
> > 
> > Oh, sorry. I confused it was the inline_data conversion. ;)
> > Yup, we can avoid entire f2fs_lock_op like this. And we can avoid IPU as well,
> > but it's quite difficult to detect that.
> 
> Seems when there is a large number of dirty inline data in page cache, then
> trigger intensively writeback and CP can run out of free space?

I expect that f2fs_balance_fs() will hopefully block them.

Thanks,

> 
> Thanks,
> 
> > 
> >>From 146e4c1ca458b1e33bf7f658f8796a8763e67a4e Mon Sep 17 00:00:00 2001
> > From: Yunlei He <heyunlei@huawei.com>
> > Date: Thu, 23 Feb 2017 20:31:20 +0800
> > Subject: [PATCH] f2fs: no need lock_op in f2fs_write_inline_data
> > 
> > Similar as f2fs_write_inode, f2fs_write_inline_data just
> > mark inode page dirty, so it's no need to write inline data
> > under read lock of cp_rwsem.
> > 
> > Signed-off-by: Yunlei He <heyunlei@huawei.com>
> > Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
> > ---
> >  fs/f2fs/data.c | 7 +++++--
> >  1 file changed, 5 insertions(+), 2 deletions(-)
> > 
> > diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
> > index 80f9863dc4b0..9e51c5e40ce1 100644
> > --- a/fs/f2fs/data.c
> > +++ b/fs/f2fs/data.c
> > @@ -1414,9 +1414,12 @@ static int __write_data_page(struct page *page, bool *submitted,
> >  		goto redirty_out;
> >  
> >  	err = -EAGAIN;
> > -	f2fs_lock_op(sbi);
> > -	if (f2fs_has_inline_data(inode))
> > +	if (f2fs_has_inline_data(inode)) {
> >  		err = f2fs_write_inline_data(inode, page);
> > +		if (!err)
> > +			goto out;
> > +	}
> > +	f2fs_lock_op(sbi);
> >  	if (err == -EAGAIN)
> >  		err = do_write_data_page(&fio);
> >  	if (F2FS_I(inode)->last_disk_size < psize)
> > 
> 
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot

      parent reply	other threads:[~2017-02-25  2:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-23 12:31 [PATCH] f2fs: no need lock_op in f2fs_write_inline_data Yunlei He
2017-02-23 19:45 ` Jaegeuk Kim
2017-02-24  3:29   ` heyunlei
2017-02-24 19:58     ` Jaegeuk Kim
2017-02-25  0:59       ` Chao Yu
2017-02-25  1:58         ` heyunlei
2017-02-25  2:10         ` 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=20170225021023.GC50867@jaegeuk.local \
    --to=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --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).