[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AM4PR0501MB2322FCCB9151D3047C46BC93AA360@AM4PR0501MB2322.eurprd05.prod.outlook.com>
Date: Mon, 18 Jul 2016 07:06:16 +0000
From: Noam Camus <noamca@...lanox.com>
To: Pan Xinhui <xinhui@...ux.vnet.ibm.com>,
"decot@...glers.com" <decot@...glers.com>
CC: "ben@...adent.org.uk" <ben@...adent.org.uk>,
"davem@...emloft.net" <davem@...emloft.net>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v3] lib/bitmap.c: enhance bitmap syntax
> From: Pan Xinhui [mailto:xinhui@...ux.vnet.ibm.com]
> Sent: Sunday, July 17, 2016 4:59 PM
>>
>> I really think it is better to implement one function to generic a string which contanis the cpus you want to boot on, then pass this string to __bitmap_parselist.
>>
> sorry, typos.
> generic -> generate.
Please explain how this will solve the syntax issue Ben commented on?
Another syntax which might be simpler is:
<first cpu-last cpu>:<numcpus selected from group>/<cpus group size>
e.g.
0-1023:1/2 <==> 0,2,4,...,1022
1-1023:1/2 <==> 1,3,5,...,1023
So basically no need for modulo only divide the list into groups of cpus and for each group choose cpus from group start.
It is basically achieves same and hopefully more simpler and more eligible for such generic code.
Please let me know what you think?
Is it good direction to change the syntax, or that I should turn into different approach (like Pan suggested)?
Noam.
Powered by blists - more mailing lists