Re: [PATCH 1/5] lib: make bitmap_parselist_user() a wrapper on bitmap_parselist()

2019-04-16 Thread Andy Shevchenko
On Mon, Apr 15, 2019 at 11:37:57PM -0700, Yury Norov wrote: > From: Yury Norov > > Currently we parse user data byte after byte which leads to > overcomplification of parsing algorithm. The only user of > bitmap_parselist_user() is not performance-critical, and so we > can duplicate user data to

[PATCH 1/5] lib: make bitmap_parselist_user() a wrapper on bitmap_parselist()

2019-04-16 Thread Yury Norov
From: Yury Norov Currently we parse user data byte after byte which leads to overcomplification of parsing algorithm. The only user of bitmap_parselist_user() is not performance-critical, and so we can duplicate user data to kernel buffer and simply call bitmap_parselist(). This rework lets us

Re: [PATCH 1/5] lib: make bitmap_parselist_user() a wrapper on bitmap_parselist()

2019-04-08 Thread Andy Shevchenko
On Fri, Apr 05, 2019 at 08:32:07PM +0300, Yury Norov wrote: > Currently we parse user data byte after byte which leads to > overcomplification of parsing algorithm. The only user of > bitmap_parselist_user() is not performance-critical, and so we > can duplicate user data to kernel buffer and

[PATCH 1/5] lib: make bitmap_parselist_user() a wrapper on bitmap_parselist()

2019-04-05 Thread Yury Norov
Currently we parse user data byte after byte which leads to overcomplification of parsing algorithm. The only user of bitmap_parselist_user() is not performance-critical, and so we can duplicate user data to kernel buffer and simply call bitmap_parselist(). This rework lets us unify and simplify

Re: [PATCH 1/5] lib: make bitmap_parselist_user() a wrapper on bitmap_parselist()

2019-04-03 Thread Andy Shevchenko
On Wed, Apr 03, 2019 at 02:17:39PM +0200, Rasmus Villemoes wrote: > On 03/04/2019 13.17, Andy Shevchenko wrote: > > On Wed, Apr 03, 2019 at 02:15:22PM +0300, Andy Shevchenko wrote: > >> On Wed, Apr 03, 2019 at 07:45:36AM +0300, Yury Norov wrote: > >>> Currently we parse user data byte after byte

Re: [PATCH 1/5] lib: make bitmap_parselist_user() a wrapper on bitmap_parselist()

2019-04-03 Thread Rasmus Villemoes
On 03/04/2019 13.17, Andy Shevchenko wrote: > On Wed, Apr 03, 2019 at 02:15:22PM +0300, Andy Shevchenko wrote: >> On Wed, Apr 03, 2019 at 07:45:36AM +0300, Yury Norov wrote: >>> Currently we parse user data byte after byte which leads to >>> overcomplification of parsing algorithm. The only user

Re: [PATCH 1/5] lib: make bitmap_parselist_user() a wrapper on bitmap_parselist()

2019-04-03 Thread Andy Shevchenko
On Wed, Apr 03, 2019 at 02:15:22PM +0300, Andy Shevchenko wrote: > On Wed, Apr 03, 2019 at 07:45:36AM +0300, Yury Norov wrote: > > Currently we parse user data byte after byte which leads to > > overcomplification of parsing algorithm. The only user of > > bitmap_parselist_user() is not

Re: [PATCH 1/5] lib: make bitmap_parselist_user() a wrapper on bitmap_parselist()

2019-04-03 Thread Andy Shevchenko
On Wed, Apr 03, 2019 at 07:45:36AM +0300, Yury Norov wrote: > Currently we parse user data byte after byte which leads to > overcomplification of parsing algorithm. The only user of > bitmap_parselist_user() is not performance-critical, and so we > can copy user data to kernel buffer and simply

[PATCH 1/5] lib: make bitmap_parselist_user() a wrapper on bitmap_parselist()

2019-04-02 Thread Yury Norov
Currently we parse user data byte after byte which leads to overcomplification of parsing algorithm. The only user of bitmap_parselist_user() is not performance-critical, and so we can copy user data to kernel buffer and simply call bitmap_parselist(). This rework lets us unify and simplify