From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Chris Metcalf <cmetcalf-kv+TWInifGbQT0dZR+AlfA@public.gmane.org>,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: [patch] CPU_SET.3: clarify language about "available" cpus
Date: Mon, 04 May 2015 15:13:24 +0200 [thread overview]
Message-ID: <55477074.6010903@gmail.com> (raw)
In-Reply-To: <4CD2F4CB.7020807-kv+TWInifGbQT0dZR+AlfA@public.gmane.org>
Chris,
On 11/04/2010 07:00 PM, Chris Metcalf wrote:
> The CPU_SET.3 man page uses the adjective "available" when explaining what
> the argument to CPU_SET() means. This is confusing, since "available"
> isn't well-defined. The kernel has a set of adjectives (possible, present,
> online, and active) that qualify cpus, but normally none of these are what
> the cpu_set_t bit index means: it's just "which cpu", using the kernel's
> internal numbering system, even if that cpu isn't possible or present.
>
> This change removes the word "available" and adds a sentence warning that
> cpu sets may not be contiguous due to dynamic cpu hotplug, etc.
Long after the fact, I've applied this patch.
Cheers,
Michael
> --- man3/CPU_SET.3.orig 2010-11-04 13:53:13.714684000 -0400
> +++ man3/CPU_SET.3 2010-11-04 13:54:59.972042000 -0400
> @@ -124,11 +124,14 @@
> argument is specified, it should not produce side effects,
> since the above macros may evaluate the argument more than once.
> .PP
> -The first available CPU on the system corresponds to a
> +The first CPU on the system corresponds to a
> .I cpu
> value of 0, the next CPU corresponds to a
> .I cpu
> value of 1, and so on.
> +No assumptions should be made about particular CPUs being
> +available, or the set of CPUs being contiguous, since CPUs can
> +be taken offline dynamically or be otherwise absent.
> The constant
> .B CPU_SETSIZE
> (currently 1024) specifies a value one greater than the maximum CPU
>
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-05-04 13:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 18:00 [patch] CPU_SET.3: clarify language about "available" cpus Chris Metcalf
[not found] ` <4CD2F4CB.7020807-kv+TWInifGbQT0dZR+AlfA@public.gmane.org>
2015-05-04 13:13 ` Michael Kerrisk (man-pages) [this message]
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=55477074.6010903@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=cmetcalf-kv+TWInifGbQT0dZR+AlfA@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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.