From: Paul Jackson <pj@sgi.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: ak@suse.de, torvalds@osdl.org, ak@muc.de, akpm@osdl.org,
linux-arch@vger.kernel.org
Subject: Re: [PATCH] Fix argument checking in sched_setaffinity
Date: Tue, 7 Sep 2004 15:55:30 -0700 [thread overview]
Message-ID: <20040907155530.5008c02c.pj@sgi.com> (raw)
In-Reply-To: <20040907214408.GB27284@linux-mips.org>
Ralf wrote:
> Same situation here for mips64. sched_setaffinity() is established and
> being used in applications, including commercial products so changing is
> not an option.
Well ... not an option unless Linus makes it one. It would be a win
in the long term, I think. We could introduce a new system call, and
mark this one for eventual removal.
Meanwhile, if sched_setaffinity() is being used in products we can't
really test, then that seems to me to be one more good reason to back
out the API tweaking that Andi and Linus have been doing to it this
last week, and just leave it be, as it was a week ago.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
next prev parent reply other threads:[~2004-09-07 22:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040831183655.58d784a3.pj@sgi.com>
[not found] ` <20040904133701.GE33964@muc.de>
[not found] ` <20040904171417.67649169.pj@sgi.com>
[not found] ` <Pine.LNX.4.58.0409041717230.4735@ppc970.osdl.org>
[not found] ` <20040904180548.2dcdd488.pj@sgi.com>
[not found] ` <Pine.LNX.4.58.0409041827280.2331@ppc970.osdl.org>
[not found] ` <20040904204850.48b7cfbd.pj@sgi.com>
[not found] ` <Pine.LNX.4.58.0409042055460.2331@ppc970.osdl.org>
[not found] ` <20040904211749.3f713a8a.pj@sgi.com>
[not found] ` <20040904215205.0a067ab8.pj@sgi.com>
[not found] ` <20040906182330.GA79122@muc.de>
[not found] ` <Pine.LNX.4.58.0409061147220.28608@ppc970.osdl.org>
[not found] ` <20040906141142.663941fb.pj@sgi.com>
2004-09-07 14:40 ` [PATCH] Fix argument checking in sched_setaffinity Linus Torvalds
2004-09-07 14:48 ` Geert Uytterhoeven
2004-09-07 14:49 ` Andi Kleen
2004-09-07 21:44 ` Ralf Baechle
2004-09-07 22:55 ` Paul Jackson [this message]
2004-09-08 6:58 ` Andi Kleen
2004-09-08 7:26 ` Paul Jackson
2004-09-08 0:26 ` Anton Blanchard
2004-09-07 14:50 ` Matthew Wilcox
2004-09-08 0:24 ` Anton Blanchard
2004-09-08 0:33 ` [PATCH] [ppc64] compat_get_bitmap/compat_put_bitmap Anton Blanchard
2004-09-08 0:40 ` [PATCH] [ppc64] Fix compat cpu affinity on big endian 64bit Anton Blanchard
2004-09-08 0:43 ` [PATCH] [ppc64] Fix compat NUMA API " Anton Blanchard
2004-09-08 5:22 ` [PATCH] [ppc64] Fix compat cpu affinity " Andrew Morton
2004-09-08 5:34 ` Anton Blanchard
2004-09-08 5:43 ` Andrew Morton
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=20040907155530.5008c02c.pj@sgi.com \
--to=pj@sgi.com \
--cc=ak@muc.de \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-arch@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox