From: Chao Yu <chao2.yu@samsung.com>
To: jaegeuk.kim@samsung.com
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
'谭姝' <shu.tan@samsung.com>
Subject: RE: [f2fs-dev] [PATCH 2/5] f2fs: add unlikely macro for compiler optimization
Date: Mon, 02 Dec 2013 12:32:04 +0800 [thread overview]
Message-ID: <000001ceef17$9205e830$b611b890$@samsung.com> (raw)
In-Reply-To: <1385720057.2417.46.camel@kjgkr>
Hi Kim,
> -----Original Message-----
> From: Jaegeuk Kim [mailto:jaegeuk.kim@samsung.com]
> Sent: Friday, November 29, 2013 6:14 PM
> To: Chao Yu
> Cc: linux-fsdevel@vger.kernel.org; linux-kernel@vger.kernel.org; linux-f2fs-devel@lists.sourceforge.net; 谭姝
> Subject: Re: [f2fs-dev] [PATCH 2/5] f2fs: add unlikely macro for compiler optimization
>
> Hi,
>
> Could you make a patch to add *unlikely* as many as possible across the
> whole source files at once?
> It is wasteful to add it with a bunch of patches at multiple times.
Alright, I will work on this.
>
> And please write descriptions for all the patches even if nothing is
> special.
> In this case, why should we set *unlikely* for checking this condition?
Got it.
Regards,
Yu
>
> Thanks,
>
> 2013-11-28 (목), 15:42 +0800, Chao Yu:
> > Signed-off-by: Chao Yu <chao2.yu@samsung.com>
> > ---
> > fs/f2fs/node.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/fs/f2fs/node.c b/fs/f2fs/node.c
> > index 0fe9a97..954155b 100644
> > --- a/fs/f2fs/node.c
> > +++ b/fs/f2fs/node.c
> > @@ -1160,7 +1160,7 @@ int wait_on_node_pages_writeback(struct f2fs_sb_info *sbi, nid_t ino)
> > struct page *page = pvec.pages[i];
> >
> > /* until radix tree lookup accepts end_index */
> > - if (page->index > end)
> > + if (unlikely(page->index > end))
> > continue;
> >
> > if (ino && ino_of_node(page) == ino) {
>
> --
> Jaegeuk Kim
> Samsung
prev parent reply other threads:[~2013-12-02 4:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 7:42 Chao Yu
2013-11-29 10:14 ` Jaegeuk Kim
2013-12-02 4:32 ` 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='000001ceef17$9205e830$b611b890$@samsung.com' \
--to=chao2.yu@samsung.com \
--cc=jaegeuk.kim@samsung.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shu.tan@samsung.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
Powered by JetHome