From: Andrew Morton <akpm@linux-foundation.org>
To: Noam Camus <noamca@mellanox.com>
Cc: <decot@googlers.com>, <ben@decadent.org.uk>,
<davem@davemloft.net>, <linux-kernel@vger.kernel.org>,
<xinhui@linux.vnet.ibm.com>
Subject: Re: [PATCH v4] lib/bitmap.c: enhance bitmap syntax
Date: Thu, 8 Sep 2016 15:19:33 -0700 [thread overview]
Message-ID: <20160908151933.1f48a10e757e5af5435f8daa@linux-foundation.org> (raw)
In-Reply-To: <1473348805-7145-1-git-send-email-noamca@mellanox.com>
On Thu, 8 Sep 2016 18:33:25 +0300 Noam Camus <noamca@mellanox.com> wrote:
> 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 syntax 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.:
> <cpus range>:sed_size/group_size
>
> For example, above map can be described in new syntax like this:
> 0-4095:8/16
There should be some updates to the user-facing documentation, please.
Documentation/kernel-parameters.txt, mainly. Which boot parameters
does this affect? For example, I think it accidentally alters
isolcpus=?
It would be useful to see the patch which wires this up (to arch/arc?).
next prev parent reply other threads:[~2016-09-08 22:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-16 7:57 [PATCH] lib/bitmap.c: enhance map pattern Noam Camus
2016-07-16 12:09 ` Ben Hutchings
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 [this message]
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=20160908151933.1f48a10e757e5af5435f8daa@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ben@decadent.org.uk \
--cc=davem@davemloft.net \
--cc=decot@googlers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=noamca@mellanox.com \
--cc=xinhui@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.