From: Ulrich Drepper <drepper@redhat.com>
To: Jack Steiner <steiner@sgi.com>
Cc: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, travis@sgi.com,
peterz@infradead.org, rja@sgi.com, sharyath@in.ibm.com,
akpm@linux-foundation.org, tglx@linutronix.de,
kosaki.motohiro@jp.fujitsu.com, mingo@elte.hu,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:sched/urgent] sched: sched_getaffinity(): Allow less than NR_CPUS length
Date: Mon, 15 Mar 2010 09:17:06 -0700 [thread overview]
Message-ID: <4B9E5D82.6020101@redhat.com> (raw)
In-Reply-To: <20100315160454.GA8211@sgi.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/15/2010 09:04 AM, Jack Steiner wrote:
> I'm running on a distro kernel that has NR_CPUS=4096. Glibc has also has a
> definition of __CPU_SETSIZE (I assume this change was made by the distro but
> am not certain):
This isn't upstream and it cannot. Whoever make this change doesn't
know what binary compatibility means. The size has always been 1024 bits.
- --
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAkueXYIACgkQ2ijCOnn/RHQJPQCbBvh+Mi7ZrHaQcVxEkglIj+Pz
j7UAoJaBCpD2a5KbAR1VGkM7orp+GBhY
=T78A
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-03-15 16:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 7:15 [PATCH] sched: sched_getaffinity() allow less than NR_CPUS length KOSAKI Motohiro
2010-03-12 16:08 ` Ulrich Drepper
2010-03-15 7:43 ` [tip:sched/urgent] sched: sched_getaffinity(): Allow " tip-bot for KOSAKI Motohiro
2010-03-15 16:04 ` Jack Steiner
2010-03-15 16:17 ` Ulrich Drepper [this message]
2010-03-16 17:10 ` Ingo Molnar
2010-03-17 0:36 ` KOSAKI Motohiro
2010-03-17 10:03 ` [tip:sched/urgent] sched: Use proper type in sched_getaffinity() tip-bot for KOSAKI Motohiro
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=4B9E5D82.6020101@redhat.com \
--to=drepper@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rja@sgi.com \
--cc=sharyath@in.ibm.com \
--cc=steiner@sgi.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=travis@sgi.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.