From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Andrew Morton <akpm@linux-foundation.org>,
Amir Vadai <amirv@mellanox.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpumask: kill loop in cpumask_next_and()
Date: Sat, 31 Jan 2015 20:39:31 +0900 [thread overview]
Message-ID: <20150131113931.GC2299@swordfish> (raw)
In-Reply-To: <1421335361-1752-1-git-send-email-sergey.senozhatsky@gmail.com>
On (01/16/15 00:22), Sergey Senozhatsky wrote:
>
> cpumask_next_and() does cpumask_next() src1 in a loop and tests if found
> cpu is alsop present in src2. remove that loop and perform cpumask_and()
> of src1 and src2 first and use to find cpumask_next() intead.
>
Hello,
did you have any chance to review this patch? let me know
if you want me to resend (I made some nasty typos in the commit
message).
-ss
> Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
> ---
> lib/cpumask.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/lib/cpumask.c b/lib/cpumask.c
> index b6513a9..5ab1553 100644
> --- a/lib/cpumask.c
> +++ b/lib/cpumask.c
> @@ -37,10 +37,11 @@ EXPORT_SYMBOL(__next_cpu_nr);
> int cpumask_next_and(int n, const struct cpumask *src1p,
> const struct cpumask *src2p)
> {
> - while ((n = cpumask_next(n, src1p)) < nr_cpu_ids)
> - if (cpumask_test_cpu(n, src2p))
> - break;
> - return n;
> + struct cpumask tmp;
> +
> + if (cpumask_and(&tmp, src1p, src2p))
> + return cpumask_next(n, &tmp);
> + return nr_cpu_ids;
> }
> EXPORT_SYMBOL(cpumask_next_and);
>
> --
> 2.2.2
>
prev parent reply other threads:[~2015-01-31 11:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 15:22 [PATCH] cpumask: kill loop in cpumask_next_and() Sergey Senozhatsky
2015-01-31 11:39 ` Sergey Senozhatsky [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=20150131113931.GC2299@swordfish \
--to=sergey.senozhatsky@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=amirv@mellanox.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.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