From: Joe Perches <joe@perches.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Yang Shi <yang.shi@linux.alibaba.com>
Cc: kirill.shutemov@linux.intel.com, hughd@google.com,
mhocko@kernel.org, hch@infradead.org, viro@zeniv.linux.org.uk,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC v5 PATCH] mm: shmem: make stat.st_blksize return huge page size if THP is on
Date: Tue, 01 May 2018 00:05:48 -0700 [thread overview]
Message-ID: <e854ad5b8798efc2e33af153c4bdae2c16031e54.camel@perches.com> (raw)
In-Reply-To: <20180430164000.00f92084ecb1876e481c6a11@linux-foundation.org>
On Mon, 2018-04-30 at 16:40 -0700, Andrew Morton wrote:
> On Wed, 25 Apr 2018 22:13:53 +0800 Yang Shi <yang.shi@linux.alibaba.com> wrote:
>
> > Since tmpfs THP was supported in 4.8, hugetlbfs is not the only
> > filesystem with huge page support anymore. tmpfs can use huge page via
> > THP when mounting by "huge=" mount option.
[]
> > @@ -571,6 +571,16 @@ static unsigned long shmem_unused_huge_shrink(struct shmem_sb_info *sbinfo,
> > }
> > #endif /* CONFIG_TRANSPARENT_HUGE_PAGECACHE */
> >
> > +static inline bool is_huge_enabled(struct shmem_sb_info *sbinfo)
> > +{
> > + if (IS_ENABLED(CONFIG_TRANSPARENT_HUGE_PAGECACHE) &&
> > + (shmem_huge == SHMEM_HUGE_FORCE || sbinfo->huge) &&
> > + shmem_huge != SHMEM_HUGE_DENY)
> > + return true;
> > + else
> > + return false;
> > +}
>
> Nit: we don't need that `else'. Checkpatch normally warns about this,
> but not in this case.
because there are those that like symmetry.
> --- a/mm/shmem.c~mm-shmem-make-statst_blksize-return-huge-page-size-if-thp-is-on-fix
> +++ a/mm/shmem.c
> @@ -577,8 +577,7 @@ static inline bool is_huge_enabled(struc
> (shmem_huge == SHMEM_HUGE_FORCE || sbinfo->huge) &&
> shmem_huge != SHMEM_HUGE_DENY)
> return true;
> - else
> - return false;
> + return false;
> }
Perhaps this case is better without the if/else as just
return <logic>;
next prev parent reply other threads:[~2018-05-01 7:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 14:13 Yang Shi
2018-04-25 14:49 ` Kirill A. Shutemov
2018-04-25 15:23 ` Christoph Hellwig
2018-04-30 23:40 ` Andrew Morton
2018-05-01 7:05 ` Joe Perches [this message]
2018-05-01 6:32 ` Hugh Dickins
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=e854ad5b8798efc2e33af153c4bdae2c16031e54.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=hughd@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=yang.shi@linux.alibaba.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