From: Uladzislau Rezki <urezki@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Uladzislau Rezki (Sony)" <urezki@gmail.com>,
Roman Gushchin <guro@fb.com>, Michal Hocko <mhocko@suse.com>,
Matthew Wilcox <willy@infradead.org>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>,
Thomas Garnier <thgarnie@google.com>,
Oleksiy Avramchenko <oleksiy.avramchenko@sonymobile.com>,
Steven Rostedt <rostedt@goodmis.org>,
Joel Fernandes <joelaf@google.com>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH 1/1] lib/test_vmalloc: do not create cpumask_t variable on stack
Date: Fri, 19 Apr 2019 13:06:56 +0200 [thread overview]
Message-ID: <20190419110656.znni5hdojf42iq5k@pc636> (raw)
In-Reply-To: <20190418151033.9e46ec06c1d7482e6dee14bc@linux-foundation.org>
On Thu, Apr 18, 2019 at 03:10:33PM -0700, Andrew Morton wrote:
> On Thu, 18 Apr 2019 21:39:25 +0200 "Uladzislau Rezki (Sony)" <urezki@gmail.com> wrote:
>
> > On my "Intel(R) Xeon(R) W-2135 CPU @ 3.70GHz" system(12 CPUs)
> > i get the warning from the compiler about frame size:
> >
> > <snip>
> > warning: the frame size of 1096 bytes is larger than 1024 bytes
> > [-Wframe-larger-than=]
> > <snip>
> >
> > the size of cpumask_t depends on number of CPUs, therefore just
> > make use of cpumask_of() in set_cpus_allowed_ptr() as a second
> > argument.
> >
> > ...
> L
> > --- a/lib/test_vmalloc.c
> > +++ b/lib/test_vmalloc.c
> > @@ -383,14 +383,14 @@ static void shuffle_array(int *arr, int n)
> > static int test_func(void *private)
> > {
> > struct test_driver *t = private;
> > - cpumask_t newmask = CPU_MASK_NONE;
> > int random_array[ARRAY_SIZE(test_case_array)];
> > int index, i, j, ret;
> > ktime_t kt;
> > u64 delta;
> >
> > - cpumask_set_cpu(t->cpu, &newmask);
> > - set_cpus_allowed_ptr(current, &newmask);
> > + ret = set_cpus_allowed_ptr(current, cpumask_of(t->cpu));
> > + if (ret < 0)
> > + pr_err("Failed to set affinity to %d CPU\n", t->cpu);
> >
> > for (i = 0; i < ARRAY_SIZE(test_case_array); i++)
> > random_array[i] = i;
>
> lgtm.
>
> While we're in there...
>
>
> From: Andrew Morton <akpm@linux-foundation.org>
> Subject: lib/test_vmalloc.c:test_func(): eliminate local `ret'
>
> Local 'ret' is unneeded and was poorly named: the variable `ret' generally
> means the "the value which this function will return".
>
> Cc: Roman Gushchin <guro@fb.com>
> Cc: Uladzislau Rezki <urezki@gmail.com>
> Cc: Michal Hocko <mhocko@suse.com>
> Cc: Matthew Wilcox <willy@infradead.org>
> Cc: Thomas Garnier <thgarnie@google.com>
> Cc: Oleksiy Avramchenko <oleksiy.avramchenko@sonymobile.com>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Cc: Joel Fernandes <joelaf@google.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Ingo Molnar <mingo@elte.hu>
> Cc: Tejun Heo <tj@kernel.org>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
> lib/test_vmalloc.c | 8 +++-----
> 1 file changed, 3 insertions(+), 5 deletions(-)
>
> --- a/lib/test_vmalloc.c~a
> +++ a/lib/test_vmalloc.c
> @@ -384,12 +384,11 @@ static int test_func(void *private)
> {
> struct test_driver *t = private;
> int random_array[ARRAY_SIZE(test_case_array)];
> - int index, i, j, ret;
> + int index, i, j;
> ktime_t kt;
> u64 delta;
>
> - ret = set_cpus_allowed_ptr(current, cpumask_of(t->cpu));
> - if (ret < 0)
> + if (set_cpus_allowed_ptr(current, cpumask_of(t->cpu)) < 0)
> pr_err("Failed to set affinity to %d CPU\n", t->cpu);
>
> for (i = 0; i < ARRAY_SIZE(test_case_array); i++)
> @@ -415,8 +414,7 @@ static int test_func(void *private)
>
> kt = ktime_get();
> for (j = 0; j < test_repeat_count; j++) {
> - ret = test_case_array[index].test_func();
> - if (!ret)
> + if (!test_case_array[index].test_func())
> per_cpu_test_data[t->cpu][index].test_passed++;
> else
> per_cpu_test_data[t->cpu][index].test_failed++;
> _
>
Agree with your slight update.
Thank you!
--
Vlad Rezki
next prev parent reply other threads:[~2019-04-19 11:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 19:39 Uladzislau Rezki (Sony)
2019-04-18 22:10 ` Andrew Morton
2019-04-19 11:06 ` Uladzislau Rezki [this message]
2019-04-19 19:49 ` Roman Gushchin
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=20190419110656.znni5hdojf42iq5k@pc636 \
--to=urezki@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=guro@fb.com \
--cc=joelaf@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=mingo@elte.hu \
--cc=oleksiy.avramchenko@sonymobile.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=thgarnie@google.com \
--cc=tj@kernel.org \
--cc=willy@infradead.org \
/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