public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: akpm@linux-foundation.org
Cc: sergey.senozhatsky@gmail.com, amirv@mellanox.com,
	davem@davemloft.net, tj@kernel.org, mm-commits@vger.kernel.org,
	peterz@infradead.org, bp@alien8.de, linux-kernel@vger.kernel.org,
	sergey.senozhatsky.work@gmail.com
Subject: Re: + cpumask-dont-perform-while-loop-in-cpumask_next_and.patch added to -mm tree
Date: Mon, 15 Jun 2015 23:38:59 +0900	[thread overview]
Message-ID: <20150615143859.GC538@swordfish> (raw)
In-Reply-To: <54f4f942.PQm4OugPrxrrW9I8%akpm@linux-foundation.org>

On (03/02/15 15:58), akpm@linux-foundation.org wrote:
> ------------------------------------------------------
> From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
> Subject: cpumask: don't perform while loop in cpumask_next_and()
> 
> cpumask_next_and() is looking for cpumask_next() in src1 in a loop and
> tests if found cpu is also present in src2. remove that loop, perform
> cpumask_and() of src1 and src2 first and use that new mask to find
> cpumask_next().
> 
> Apart from removing while loop, ./bloat-o-meter on x86_64 shows
> add/remove: 0/0 grow/shrink: 0/1 up/down: 0/-8 (-8)
> function                                     old     new   delta
> cpumask_next_and                              62      54      -8
> 


Sir,

Please revert this commit.

It does awful things on really big machines (spotted by Peter Zijlstra).


	-ss

> Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
> Cc: Tejun Heo <tj@kernel.org>
> Cc: "David S. Miller" <davem@davemloft.net>
> Cc: Amir Vadai <amirv@mellanox.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
> 
>  lib/cpumask.c |    9 +++++----
>  1 file changed, 5 insertions(+), 4 deletions(-)
> 
> diff -puN lib/cpumask.c~cpumask-dont-perform-while-loop-in-cpumask_next_and lib/cpumask.c
> --- a/lib/cpumask.c~cpumask-dont-perform-while-loop-in-cpumask_next_and
> +++ a/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);
>  
> _
> 
> Patches currently in -mm which might be from sergey.senozhatsky@gmail.com are
> 
> cpumask-dont-perform-while-loop-in-cpumask_next_and.patch
> lib-lz4-pull-out-constant-tables.patch
> 

           reply	other threads:[~2015-06-15 14:40 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <54f4f942.PQm4OugPrxrrW9I8%akpm@linux-foundation.org>]

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=20150615143859.GC538@swordfish \
    --to=sergey.senozhatsky@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=amirv@mellanox.com \
    --cc=bp@alien8.de \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=sergey.senozhatsky.work@gmail.com \
    --cc=tj@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