From: Pavel Machek <pavel@suse.cz>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Davide Libenzi <davidel@xmailserver.org>,
lkml <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [RFC] Scheduler queue implementation ...
Date: Thu, 20 Dec 2001 20:36:30 +0100 [thread overview]
Message-ID: <20011220203630.A204@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.40.0112091647360.996-100000@blue1.dev.mcafeelabs.com> <E16DF39-00008w-00@the-village.bc.nu>
In-Reply-To: <E16DF39-00008w-00@the-village.bc.nu>
Hi!
> > Alan, you're mixing switch mm costs with cache image reload ones.
> > Note that equal mm does not mean matching cache image, at all.
>
> They are often close to the same thing. Take a look at the constraints
> on virtually cached processors like the ARM where they _are_ the same thing.
>
> Equal mm for cpu sucking tasks often means equal cache image. On the
Really?
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.
Pavel
--
"I do not steal MS software. It is not worth it."
-- Pavel Kankovsky
next prev parent reply other threads:[~2001-12-20 21:34 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 [this message]
2001-12-20 21:42 ` Rik van Riel
2001-12-21 17:01 ` Alan Cox
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=20011220203630.A204@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.