All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Domaigne <tech-Z4JMKDdsf89Wk0Htik3J/w@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	josv-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org,
	"brian m. carlson"
	<sandals-spVehEqlxw627WubY2PhZQivdfXVPZ6z@public.gmane.org>,
	Bert Wesarg <bert.wesarg-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>,
	Stefan Puiu
	<stefanpuiuro-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>,
	Karsten Weiss
	<K.Weiss-Pt+Xe7GJXK+P2YhJcF5u+nqWYbMAw+HU@public.gmane.org>
Subject: Re: For review: pthread_attr_setaffinity_np.3
Date: Sat, 15 Nov 2008 20:51:27 +0100	[thread overview]
Message-ID: <491F283F.5000300@domaigne.com> (raw)
In-Reply-To: <cfd18e0f0811140842k78d935a3g4af1e9c81efd74d1-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hi Michael,


>>> .TH PTHREAD_ATTR_SETAFFINITY_NP 3 2008-11-05 "Linux" "Linux Programmer's
>>> Manual"
>> Title looks weird on a 80x24 terminal.
> 
> Yes.  But, hard to help -- I couldn't think of a reasonable, more
> abbreviated name for the page title.

Sure. I just reviewed using the '-pedantic' flag :-D


>>> .TP
>>> .BR EINVAL
>>> .RB ( pthread_attr_setaffinity_np ())
>>> .I cpuset
>>> specified a CPU that was outside the range
>>> permitted by the kernel data type
>>> .\" cpumask_t
>>> used to represent CPU sets.
>>> .\" The raw sched_getaffinity() system call returns the size (in bytes)
>>> .\" of the cpumask_t type.
>>> This range is determined by the kernel configuration option
>>> .BR CONFIG_NR_CPUS .
> 
> (While we're here: I changed the text of this EINVAL error to be the
> same as the revised EINVAL error text in ptherad_setaffinity_np(3).)
> 
>> <check>
>> Hmmm. What does happen if CPU set contains no CPU physically on the system
>> when the thread is created? I guess pthread_create() fails?
>> </check>
> 
> I would expect pthread_create() to fail with EINVAL, and testing
> confirms this.  (There is an EINVAL error diagnostic in
> pthread_create(3): "Invalid settings in attr".)

Fine. I expected something like that, but I didn't got the opportunity 
to check it. Thanks.


>>> .TP
>>> .B ENOMEM
>>> .RB ( pthread_attr_setaffinity_np ())
>>> Could not allocate memory.
>> Correct. However, the glibc looks somewhat suspicious to me: I had expected
>> the memory allocated by iattr->cpuset to be bounded (by the size of the
>> underlying kernel structure).
>>
>> Or perhaps I am just missing my coffeine :o
> 
> Not sure if you are suggesting that I need to change anything here?

I suggest to change the glibc code, not your description.


> .\" Copyright (c) 2008 Linux Foundation, written by Michael Kerrisk
> .\"     <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

[snip]

The revised version looks good to me.

Cheers,
Loïc.
--
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

      parent reply	other threads:[~2008-11-15 19:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-05 14:17 For review: pthread_attr_setaffinity_np.3 Michael Kerrisk
     [not found] ` <cfd18e0f0811050617h75c6ed47q31a10058fd257842-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-11-12 21:54   ` Loic Domaigne
     [not found]     ` <491B509E.6070801-Z4JMKDdsf89Wk0Htik3J/w@public.gmane.org>
2008-11-12 21:23       ` Bert Wesarg
     [not found]         ` <36ca99e90811121323u2b3895dbld7a046d0545da9b3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-11-15 10:17           ` Loic Domaigne
2008-11-14 16:42       ` Michael Kerrisk
     [not found]         ` <cfd18e0f0811140842k78d935a3g4af1e9c81efd74d1-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-11-15 19:51           ` Loic Domaigne [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=491F283F.5000300@domaigne.com \
    --to=tech-z4jmkddsf89wk0htik3j/w@public.gmane.org \
    --cc=K.Weiss-Pt+Xe7GJXK+P2YhJcF5u+nqWYbMAw+HU@public.gmane.org \
    --cc=bert.wesarg-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org \
    --cc=josv-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=sandals-spVehEqlxw627WubY2PhZQivdfXVPZ6z@public.gmane.org \
    --cc=stefanpuiuro-/E1597aS9LQAvxtiuMwx3w@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.