From: Vlastimil Babka <vbabka@suse.cz>
To: Charan Teja Kalla <quic_charante@quicinc.com>,
akpm@linux-foundation.org, nigupta@nvidia.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: compaction: fix compiler warning when CONFIG_COMPACTION=n
Date: Fri, 18 Mar 2022 16:11:39 +0100 [thread overview]
Message-ID: <845449c1-d19a-5c9e-4ccb-352dff9ec473@suse.cz> (raw)
In-Reply-To: <1647608518-20924-1-git-send-email-quic_charante@quicinc.com>
On 3/18/22 14:01, Charan Teja Kalla wrote:
> The below warning is reported when CONFIG_COMPACTION=n:
>
> mm/compaction.c:56:27: warning: 'HPAGE_FRAG_CHECK_INTERVAL_MSEC'
> defined but not used [-Wunused-const-variable=]
> 56 | static const unsigned int HPAGE_FRAG_CHECK_INTERVAL_MSEC =
> 500;
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Fix it by moving 'HPAGE_FRAG_CHECK_INTERVAL_MSEC' under
> CONFIG_COMPACTION defconfig. Also since this is just a 'static const
> int' type, use #define for it.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Charan Teja Kalla <quic_charante@quicinc.com>
Acked-by: Vlastimil Babka <vbabka@suse.cz>
> ---
> mm/compaction.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/mm/compaction.c b/mm/compaction.c
> index b4e94cd..4d86d04 100644
> --- a/mm/compaction.c
> +++ b/mm/compaction.c
> @@ -26,6 +26,11 @@
> #include "internal.h"
>
> #ifdef CONFIG_COMPACTION
> +/*
> + * Fragmentation score check interval for proactive compaction purposes.
> + */
> +#define HPAGE_FRAG_CHECK_INTERVAL_MSEC (500)
> +
> static inline void count_compact_event(enum vm_event_item item)
> {
> count_vm_event(item);
> @@ -51,11 +56,6 @@ static inline void count_compact_events(enum vm_event_item item, long delta)
> #define pageblock_end_pfn(pfn) block_end_pfn(pfn, pageblock_order)
>
> /*
> - * Fragmentation score check interval for proactive compaction purposes.
> - */
> -static const unsigned int HPAGE_FRAG_CHECK_INTERVAL_MSEC = 500;
> -
> -/*
> * Page order with-respect-to which proactive compaction
> * calculates external fragmentation, which is used as
> * the "fragmentation score" of a node/zone.
prev parent reply other threads:[~2022-03-18 15:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 13:01 Charan Teja Kalla
2022-03-18 15:11 ` Vlastimil Babka [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=845449c1-d19a-5c9e-4ccb-352dff9ec473@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nigupta@nvidia.com \
--cc=quic_charante@quicinc.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