linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] bitmap_equal memcmp optimization for s390
@ 2016-06-07  8:37 Martin Schwidefsky
  0 siblings, 0 replies; 3+ messages in thread
From: Martin Schwidefsky @ 2016-06-07  8:37 UTC (permalink / raw)
  To: linux-arch, linux-kernel, Benjamin Herrenschmidt, David S. Miller
  Cc: Martin Schwidefsky

Servus,

while working on an improved TLB flush logic for s390 I noticed that
for s390 cpumask_equal() alias bitmap_equal() can be improved for the
special case "(nbits % BITS_PER_LONG) == 0". The memcmp function can
be used in this case and we have an instruction for that ..

Trouble is that the default memcmp implementation uses a byte loop
while the __bitmap_equal function uses a loop over unsigned long.
For x86 the __bitmap_equal function is faster than memcmp, using
memcmp for the special case for all architectures is not correct.
Right now the patches uses a '#ifdef CONFIG_S390' to guard the
memcmp special case.

I hesitate to put another CONFIG_S390 into common code, alternatively
__HAVE_ARCH_MEMCMP could be used. There are 7 architectures with the
define: arc, arm64, blackfin, frv, powerpc, s390 and sparc.
Of those I guess only powerpc, s390 and sparc will have configs with
(NR_CPUS > BITS_PER_LONG). For (NR_CPUS <= BITS_PER_LONG) the xor
optimization is used.

powerpc, s390 and sparc do have optimized memcmp code, the question
is if it is faster then __bitmap_equal.

Now, CONFIG_S390 or __HAVE_ARCH_MEMCMP ?

blue skies,
  Martin

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH] bitmap_equal memcmp optimization for s390
  2016-06-09 14:26 ` David Howells
@ 2016-06-09 14:45   ` Martin Schwidefsky
  0 siblings, 0 replies; 3+ messages in thread
From: Martin Schwidefsky @ 2016-06-09 14:45 UTC (permalink / raw)
  To: David Howells
  Cc: linux-arch, linux-kernel, Benjamin Herrenschmidt, David S. Miller

On Thu, 09 Jun 2016 15:26:47 +0100
David Howells <dhowells@redhat.com> wrote:

> Martin Schwidefsky <schwidefsky@de.ibm.com> wrote:
> 
> > I hesitate to put another CONFIG_S390 into common code, alternatively
> > __HAVE_ARCH_MEMCMP could be used. There are 7 architectures with the
> > define: arc, arm64, blackfin, frv, powerpc, s390 and sparc.
> > Of those I guess only powerpc, s390 and sparc will have configs with
> > (NR_CPUS > BITS_PER_LONG). For (NR_CPUS <= BITS_PER_LONG) the xor
> > optimization is used.
> 
> FRV doesn't have __HAVE_ARCH_MEMCMP for __KERNEL__.

Yes indeed. How strange to define __HAVE_ARCH_xxx for user space only.

-- 
blue skies,
   Martin.

"Reality continues to ruin my life." - Calvin.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH] bitmap_equal memcmp optimization for s390
       [not found] <201606070837.u578Y1R5037289@mx0a-001b2d01.pphosted.com>
@ 2016-06-09 14:26 ` David Howells
  2016-06-09 14:45   ` Martin Schwidefsky
  0 siblings, 1 reply; 3+ messages in thread
From: David Howells @ 2016-06-09 14:26 UTC (permalink / raw)
  To: Martin Schwidefsky
  Cc: dhowells, linux-arch, linux-kernel, Benjamin Herrenschmidt,
	David S. Miller

Martin Schwidefsky <schwidefsky@de.ibm.com> wrote:

> I hesitate to put another CONFIG_S390 into common code, alternatively
> __HAVE_ARCH_MEMCMP could be used. There are 7 architectures with the
> define: arc, arm64, blackfin, frv, powerpc, s390 and sparc.
> Of those I guess only powerpc, s390 and sparc will have configs with
> (NR_CPUS > BITS_PER_LONG). For (NR_CPUS <= BITS_PER_LONG) the xor
> optimization is used.

FRV doesn't have __HAVE_ARCH_MEMCMP for __KERNEL__.

David

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2016-06-09 14:46 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-06-07  8:37 [PATCH] bitmap_equal memcmp optimization for s390 Martin Schwidefsky
     [not found] <201606070837.u578Y1R5037289@mx0a-001b2d01.pphosted.com>
2016-06-09 14:26 ` David Howells
2016-06-09 14:45   ` Martin Schwidefsky

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).