From: Jeff Garzik <jgarzik@pobox.com>
To: Christoph Hellwig <hch@sgi.com>
Cc: marcelo@connectiva.com.br.munich.sgi.com, rml@tech9.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] set_cpus_allowed() for 2.4
Date: Mon, 02 Dec 2002 12:24:49 -0500 [thread overview]
Message-ID: <3DEB9761.50503@pobox.com> (raw)
In-Reply-To: <20021202192652.A25938@sgi.com>
Christoph Hellwig wrote:
> now that all commercial vendors ship a backport of Ingo's O(1) scheduler
> external projects like XFS have to track those projects in addition to the
> mainline kernel.
>
> Having the common new APIs available in mainline would be a very good thing
> for those projects. We already have a proper yield() in 2.4.20, but the
> set_cpus_allowed() API as used e.g. for kernelthreads bound to CPUs is
> still missing.
>
> Any chance you could apply Robert Love's patch to add it for 2.4.21? Note
> that it does not change any existing code but just adds that interface.
Adding to that, it is also used for backporting Ingo's workqueue stuff,
which is useful and completely separate from the O(1) scheduler.
I plan on using workqueues for moving some drivers' duties to process
context where it really belongs [which in turn fixes bugs].
Jeff
next prev parent reply other threads:[~2002-12-02 17:17 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 0:26 [PATCH] set_cpus_allowed() for 2.4 Christoph Hellwig
2002-12-02 17:24 ` Jeff Garzik [this message]
2002-12-02 18:57 ` Robert Love
2002-12-03 0:51 ` Christoph Hellwig
2002-12-02 17:50 ` Martin J. Bligh
2002-12-02 18:50 ` Adrian Bunk
2002-12-02 19:12 ` Robert Love
2002-12-02 19:30 ` Andrew Morton
2002-12-02 19:50 ` Andrea Arcangeli
2002-12-03 20:49 ` Andrew Morton
2002-12-03 21:09 ` Martin J. Bligh
2002-12-04 0:09 ` Andrea Arcangeli
2002-12-04 0:06 ` Andrea Arcangeli
2002-12-04 0:30 ` Andrew Morton
2002-12-04 0:42 ` Andrea Arcangeli
2002-12-04 1:03 ` William Lee Irwin III
2002-12-04 9:25 ` William Lee Irwin III
2002-12-04 1:14 ` Andrew Morton
2002-12-04 1:21 ` Andrea Arcangeli
2002-12-04 2:14 ` Andrew Morton
2002-12-06 18:11 ` William Lee Irwin III
2002-12-08 13:23 ` Ingo Molnar
2002-12-08 19:56 ` Andrew Morton
2002-12-09 20:13 ` Ingo Molnar
2002-12-03 1:11 ` Christoph Hellwig
2002-12-02 18:59 ` Robert Love
2002-12-02 22:47 ` Alan Cox
2002-12-02 22:38 ` Christoph Hellwig
2002-12-02 22:41 ` Robert Love
2002-12-07 16:55 ` bill davidsen
-- strict thread matches above, loose matches on Subject: below --
2002-12-13 23:08 Christoph Hellwig
2002-12-13 21:34 ` Adrian Bunk
2002-12-14 4:55 ` Christoph Hellwig
2002-12-09 20:19 kernel
2002-12-09 3:02 Jim Houston
2002-10-01 23:03 Robert Love
2002-10-02 13:01 ` Christoph Hellwig
2002-10-02 15:00 ` Robert Love
2002-11-05 3:37 ` Christoph Hellwig
2002-11-06 15:32 ` Adrian Bunk
2002-11-07 21:42 ` Christoph Hellwig
2002-12-02 17:12 ` Mikael Pettersson
2002-12-03 0:51 ` Christoph Hellwig
2002-12-02 17:47 ` Mikael Pettersson
2002-12-02 19:10 ` Robert Love
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=3DEB9761.50503@pobox.com \
--to=jgarzik@pobox.com \
--cc=hch@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@connectiva.com.br.munich.sgi.com \
--cc=rml@tech9.net \
/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.