From: Ben Hutchings <ben@decadent.org.uk>
To: Noam Camus <noamca@mellanox.com>, decot@googlers.com
Cc: davem@davemloft.net, akpm@linux-foundation.org,
xinhuix.pan@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lib/bitmap.c: enhance map pattern
Date: Sat, 16 Jul 2016 13:09:41 +0100 [thread overview]
Message-ID: <1468670981.4174.89.camel@decadent.org.uk> (raw)
In-Reply-To: <1468655843-13697-1-git-send-email-noamca@mellanox.com>
[-- Attachment #1: Type: text/plain, Size: 1485 bytes --]
On Sat, 2016-07-16 at 10:57 +0300, Noam Camus wrote:
> From: Noam Camus <noamca@mellanox.com>
>
> Today there are platforms with many CPUs (up to 4K).
> Trying to boot only part of the CPUs may result in too long string.
>
> For example lets take NPS platform that is part of arch/arc.
> This platform have SMP system with 256 cores each with
> 16 HW threads (SMT machine) where HW thread appears as CPU to the kernel.
> In this example there is total of 4K CPUs.
> When one tries to boot only part of the HW threads from each core the
> string representing the map may be long...
> For example if for sake of performance we decided to boot only first half
> of HW threads of each core the map will look like:
> 0-7,16-23,32,39,...,4080-4087
>
> This patch introduce new format to accommodate with such use case.
> I added an optional postfix to a range of CPUs which will choose
> according to given modulo the desired range of reminders i.e.:
> %modulo=
This is a fairly awful syntax, and I question whether it belongs in
this generic code.
[...]
> + * Optionally each range can be postfixed to denote that only parts of it
> + * should be set. The parts are the range of reminders modulo some value.
> + * i.e. range%mod=rem_range e.g. 0-1023%256=0-2 ==> 0,1,256,257,512,513,768,769
[...]
This example seems to be wrong - did you mean '=0-1'?
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-07-16 12:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-16 7:57 Noam Camus
2016-07-16 12:09 ` Ben Hutchings [this message]
2016-07-17 6:33 ` [PATCH v2] lib/bitmap.c: enhance bitmap syntax Noam Camus
2016-07-17 8:10 ` [PATCH v3] " Noam Camus
2016-07-17 13:50 ` Pan Xinhui
2016-07-17 13:59 ` Pan Xinhui
2016-07-18 7:06 ` Noam Camus
2016-08-01 4:53 ` Noam Camus
2016-09-06 9:12 ` Noam Camus
2016-09-06 13:36 ` Ben Hutchings
2016-09-08 15:33 ` [PATCH v4] " Noam Camus
2016-09-08 22:19 ` Andrew Morton
2016-09-11 7:40 ` [PATCH v5] " Noam Camus
2016-09-13 22:54 ` Andrew Morton
2016-09-14 6:52 ` Noam Camus
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=1468670981.4174.89.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=decot@googlers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=noamca@mellanox.com \
--cc=xinhuix.pan@intel.com \
/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
all inboxes | Powered by JetHome®