Hi Yury,
On Fri, Nov 24, 2017 at 3:30 PM, Yury Norov wrote:
> Below the updates proposed in this thread.
Thank you!
> From 959700bd7e7f586171c15a4130a9888acac02daf Mon Sep 17 00:00:00 2001
> From: Yury Norov
> Date: Wed, 22 Nov 2017
Hi Yury,
On Fri, Nov 24, 2017 at 3:30 PM, Yury Norov wrote:
> Below the updates proposed in this thread.
Thank you!
> From 959700bd7e7f586171c15a4130a9888acac02daf Mon Sep 17 00:00:00 2001
> From: Yury Norov
> Date: Wed, 22 Nov 2017 17:21:40 +0300
> Subject: [PATCH] improve lib/test_find_bit
Hi Geert, all
Below the updates proposed in this thread.
Yury
>From 959700bd7e7f586171c15a4130a9888acac02daf Mon Sep 17 00:00:00 2001
From: Yury Norov
Date: Wed, 22 Nov 2017 17:21:40 +0300
Subject: [PATCH] improve lib/test_find_bit
As suggested in review comments:
Hi Geert, all
Below the updates proposed in this thread.
Yury
>From 959700bd7e7f586171c15a4130a9888acac02daf Mon Sep 17 00:00:00 2001
From: Yury Norov
Date: Wed, 22 Nov 2017 17:21:40 +0300
Subject: [PATCH] improve lib/test_find_bit
As suggested in review comments:
* printk: align numbers
Hi Yury,
On Thu, Nov 9, 2017 at 3:07 PM, Yury Norov wrote:
> find_bit functions are widely used in the kernel, including hot paths.
> This module tests performance of that functions in 2 typical scenarios:
> randomly filled bitmap with relatively equal distribution of
Hi Yury,
On Thu, Nov 9, 2017 at 3:07 PM, Yury Norov wrote:
> find_bit functions are widely used in the kernel, including hot paths.
> This module tests performance of that functions in 2 typical scenarios:
> randomly filled bitmap with relatively equal distribution of set and
> cleared bits, and
On Tue, 14 Nov 2017 13:07:30 +0300 Yury Norov wrote:
> > Yyra, you can grab CONFIG_BENCHMARK_* namespace :-)
>
> There's no CONFIG_BENCHMARK_* namespace actually.
Alexey means you can be the first user of CONFIG_BENCHMARK_*.
> The 'CONFIG_*_BENCHMARK' is
>
On Tue, 14 Nov 2017 13:07:30 +0300 Yury Norov wrote:
> > Yyra, you can grab CONFIG_BENCHMARK_* namespace :-)
>
> There's no CONFIG_BENCHMARK_* namespace actually.
Alexey means you can be the first user of CONFIG_BENCHMARK_*.
> The 'CONFIG_*_BENCHMARK' is
> referenced only 3 times in linux
Hi Michael,
On Sun, Nov 12, 2017 at 10:33:55PM +1100, Michael Ellerman wrote:
> Yury Norov writes:
>
> > find_bit functions are widely used in the kernel, including hot paths.
> > This module tests performance of that functions in 2 typical scenarios:
> > randomly
Hi Michael,
On Sun, Nov 12, 2017 at 10:33:55PM +1100, Michael Ellerman wrote:
> Yury Norov writes:
>
> > find_bit functions are widely used in the kernel, including hot paths.
> > This module tests performance of that functions in 2 typical scenarios:
> > randomly filled bitmap with relatively
Hi Alexey, Andrew,
Thanks for comments.
On Fri, Nov 10, 2017 at 12:45:18PM +0200, Alexey Dobriyan wrote:
> On 11/10/17, Andrew Morton wrote:
> > On Thu, 9 Nov 2017 17:07:14 +0300 Yury Norov
> > wrote:
> >
> >> find_bit functions are widely
Hi Alexey, Andrew,
Thanks for comments.
On Fri, Nov 10, 2017 at 12:45:18PM +0200, Alexey Dobriyan wrote:
> On 11/10/17, Andrew Morton wrote:
> > On Thu, 9 Nov 2017 17:07:14 +0300 Yury Norov
> > wrote:
> >
> >> find_bit functions are widely used in the kernel, including hot paths.
> >> This
Yury Norov writes:
> find_bit functions are widely used in the kernel, including hot paths.
> This module tests performance of that functions in 2 typical scenarios:
> randomly filled bitmap with relatively equal distribution of set and
> cleared bits, and sparse
Yury Norov writes:
> find_bit functions are widely used in the kernel, including hot paths.
> This module tests performance of that functions in 2 typical scenarios:
> randomly filled bitmap with relatively equal distribution of set and
> cleared bits, and sparse bitmap which has 1 set bit for
On 11/10/17, Andrew Morton wrote:
> On Thu, 9 Nov 2017 17:07:14 +0300 Yury Norov
> wrote:
>
>> find_bit functions are widely used in the kernel, including hot paths.
>> This module tests performance of that functions in 2 typical scenarios:
On 11/10/17, Andrew Morton wrote:
> On Thu, 9 Nov 2017 17:07:14 +0300 Yury Norov
> wrote:
>
>> find_bit functions are widely used in the kernel, including hot paths.
>> This module tests performance of that functions in 2 typical scenarios:
>> randomly filled bitmap with relatively equal
On Thu, 9 Nov 2017 17:07:14 +0300 Yury Norov wrote:
> find_bit functions are widely used in the kernel, including hot paths.
> This module tests performance of that functions in 2 typical scenarios:
> randomly filled bitmap with relatively equal distribution of set
On Thu, 9 Nov 2017 17:07:14 +0300 Yury Norov wrote:
> find_bit functions are widely used in the kernel, including hot paths.
> This module tests performance of that functions in 2 typical scenarios:
> randomly filled bitmap with relatively equal distribution of set and
> cleared bits, and
Reviewed-By: Clement Courbet
Thanks for the addition, Yury ! I've used a modified version of v1
for measuring improvements from find_next_and_bit() on x86 and arm
and found it very useful.
Reviewed-By: Clement Courbet
Thanks for the addition, Yury ! I've used a modified version of v1
for measuring improvements from find_next_and_bit() on x86 and arm
and found it very useful.
find_bit functions are widely used in the kernel, including hot paths.
This module tests performance of that functions in 2 typical scenarios:
randomly filled bitmap with relatively equal distribution of set and
cleared bits, and sparse bitmap which has 1 set bit for 500 cleared bits.
On ThunderX
find_bit functions are widely used in the kernel, including hot paths.
This module tests performance of that functions in 2 typical scenarios:
randomly filled bitmap with relatively equal distribution of set and
cleared bits, and sparse bitmap which has 1 set bit for 500 cleared bits.
On ThunderX
22 matches
Mail list logo