mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: pavel@suse.cz (Pavel Machek)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
	davidel@xmailserver.org (Davide Libenzi),
	linux-kernel@vger.kernel.org (lkml),
	torvalds@transmeta.com (Linus Torvalds)
Subject: Re: [RFC] Scheduler queue implementation ...
Date: Fri, 21 Dec 2001 17:01:11 +0000 (GMT)	[thread overview]
Message-ID: <E16HT2l-0000oP-00@the-village.bc.nu> (raw)
In-Reply-To: <20011220203630.A204@elf.ucw.cz> from "Pavel Machek" at Dec 20, 2001 08:36:30 PM

> 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
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)

  parent reply	other threads:[~2001-12-21 16:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-10  0:33 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 [this message]
2001-12-21 19:21           ` Pavel Machek
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=E16HT2l-0000oP-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=davidel@xmailserver.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®