From: Pavel Machek <pavel@suse.cz>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Scheduler queue implementation ...
Date: Fri, 21 Dec 2001 20:21:13 +0100 [thread overview]
Message-ID: <20011221202113.D415@elf.ucw.cz> (raw)
In-Reply-To: <20011220203630.A204@elf.ucw.cz> <E16HT2l-0000oP-00@the-village.bc.nu>
In-Reply-To: <E16HT2l-0000oP-00@the-village.bc.nu>
Hi!
> > I'd guess that if cpu-bound software wants to use clone(CLONE_VM) to
> > gain some performance, it should better work "mostly" in different
> > memory areas on different cpus... But I could be wrong.
>
> Lots of people use shared mm objects and threads for things like UI
> rather
But ... UI performance should not matter much. And that is *abuse* of
threads.
> than just for cpu hogging. If they have multiple cpu hogs doing that then
> they want punishing (or better yet sending a copy of a document on
> caches)
If I have a raytracer, and want to explore 8 cpus, how do I do that?
Separate scene into 8 pieces, make sure no r/w data are shared, and
clone(CLONE_VM). Are there other ways? [I do not know if people are
really doing it like that. *I* would do it that way. Is it bad?]
Pavel
--
"I do not steal MS software. It is not worth it."
-- Pavel Kankovsky
next prev parent reply other threads:[~2001-12-22 10:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-10 0:33 [RFC] Scheduler queue implementation Davide Libenzi
2001-12-10 0:49 ` Alan Cox
2001-12-10 0:57 ` Davide Libenzi
2001-12-10 1:16 ` Alan Cox
2001-12-10 2:36 ` Davide Libenzi
2001-12-20 19:36 ` Pavel Machek
2001-12-20 21:42 ` Rik van Riel
2001-12-21 17:01 ` Alan Cox
2001-12-21 19:21 ` Pavel Machek [this message]
2001-12-22 14:23 ` Alan Cox
2001-12-10 0:52 ` Alan Cox
2001-12-10 1:06 ` Davide Libenzi
2001-12-10 1:18 ` Alan Cox
2001-12-10 1:38 ` Davide Libenzi
2001-12-10 1:52 ` Alan Cox
2001-12-10 3:06 ` Davide Libenzi
2001-12-10 23:03 ` Mike Kravetz
2001-12-10 23:30 ` Davide Libenzi
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=20011221202113.D415@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.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