Re: lib/58679: sched_getaffinity_np() always returns an empty set

["Ondřej Surý via gnats" <gnats-admin%NetBSD.org@localhost>]

The following reply was made to PR lib/58679; it has been noted by GNATS.

From: =?utf-8?Q?Ond=C5=99ej_Sur=C3=BD?= <ondrej%sury.org@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: lib-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
 netbsd-bugs%netbsd.org@localhost
Subject: Re: lib/58679: sched_getaffinity_np() always returns an empty set
Date: Thu, 19 Sep 2024 16:25:07 +0200

 In that case, please consider this to be a documentation bug as the NetBSD i=
 mplementation differs from sched_getaffinity (Linux) and cpuset_getaffinity (=
 FreeBSD). And it is reasonable to expect the similarity between those.
 
 As a side note, it doesn=E2=80=99t make it any easier to implement the code t=
 hat pulls the number CPUs available as one must call both sched_getaffinity_=
 np() and if that fails fallback to sysconf(). At least I expect the process d=
 oes inherit the affinity from the parent, right?
 
 Thank you,
 Ondrej
 --
 Ond=C5=99ej Sur=C3=BD (He/Him)
 
 > On 19. 9. 2024, at 14:55, Martin Husemann via gnats <gnats-admin%netbsd.or@localhost=
 g> wrote:
 >=20
 > The default affinity of a process in NetBSD is the empty set (that is:
 > no specific affinity is defined).
 >=20
 > I don't think this should be considered a bug.
 >=20
 > If you set some affinity, the sched_getaffinity* calls will return the mas=
 k
 > you set.