From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Huang Ying <ying.huang@intel.com>
Cc: Changman Lee <cm224.lee@samsung.com>,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -v2] f2fs: Remove lock from check_valid_map
Date: Sun, 7 Sep 2014 20:50:24 -0700 [thread overview]
Message-ID: <20140908035024.GA13009@jaegeuk-mac02.hsd1.ca.comcast.net> (raw)
In-Reply-To: <1410061110-31081-1-git-send-email-ying.huang@intel.com>
Hi,
On Sun, Sep 07, 2014 at 11:38:30AM +0800, Huang Ying wrote:
> Only one bit is read in check_valid_map, holding a lock to do that
> doesn't help anything except decreasing performance.
>
> Signed-off-by: Huang, Ying <ying.huang@intel.com>
> ---
>
> v2: Fixed a build warning.
>
> ---
> fs/f2fs/gc.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> --- a/fs/f2fs/gc.c
> +++ b/fs/f2fs/gc.c
> @@ -378,14 +378,11 @@ static void put_gc_inode(struct list_hea
> static int check_valid_map(struct f2fs_sb_info *sbi,
> unsigned int segno, int offset)
> {
> - struct sit_info *sit_i = SIT_I(sbi);
> struct seg_entry *sentry;
> int ret;
>
> - mutex_lock(&sit_i->sentry_lock);
> sentry = get_seg_entry(sbi, segno);
> ret = f2fs_test_bit(offset, sentry->cur_valid_map);
> - mutex_unlock(&sit_i->sentry_lock);
> return ret;
The f2fs_test_bit is not atomic, so I'm not sure this is a good approach.
How about introducing rw_semaphore?
> }
>
next prev parent reply other threads:[~2014-09-08 3:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-07 3:05 [PATCH] " Huang Ying
2014-09-07 3:38 ` [PATCH -v2] " Huang Ying
2014-09-08 3:50 ` Jaegeuk Kim [this message]
[not found] ` <CAC=cRTOdvOp=zBT986SqGXC2+iRxGzSgKdFYzTQjbAamYsGVsg@mail.gmail.com>
2014-09-09 5:13 ` Jaegeuk Kim
2014-09-09 5:43 ` Huang Ying
2014-09-09 7:41 ` Jaegeuk Kim
2014-09-09 8:04 ` Huang Ying
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=20140908035024.GA13009@jaegeuk-mac02.hsd1.ca.comcast.net \
--to=jaegeuk@kernel.org \
--cc=cm224.lee@samsung.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ying.huang@intel.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
all inboxes | Powered by JetHome®