From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Pegasus 2.6 is released
Date: Tue, 3 Feb 2009 11:07:40 -0500 [thread overview]
Message-ID: <9895aa081bff6e53edfa01c398576e7c@quanstro.net> (raw)
In-Reply-To: <13426df10902030803q33a25285k135ee01d33f50f53@mail.gmail.com>
> > Not obvious to me. In today's (well, tomorrow's) massively multicore
> > world, I would expect a remote call to a process in another core, with
> > its own instruction cache, could easily be more efficient than a local
> > procedure call.
> >
>
> well, there's remote calls and remote calls. Remote calls that go
> through some shared memory queue are one thing. But a remote call that
> goes through the kernel? You'd better have lots of work to amortize
> that cost. The packages I've seen do not.
ignorant question.
is the cost in latency or cycles? if the cost is latency
and your application is parallel, could the simple trick
of having multple outstanding help?
- erik
next prev parent reply other threads:[~2009-02-03 16:07 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-01 4:29 Kenji Arisawa
2009-02-01 4:41 ` lucio
2009-02-01 4:47 ` Kenji Arisawa
2009-02-01 4:43 ` John Barham
2009-02-01 4:50 ` andrey mirtchovski
2009-02-01 5:47 ` John Barham
2009-02-01 6:44 ` erik quanstrom
2009-02-01 7:27 ` John Barham
2009-02-01 11:12 ` Francisco J Ballesteros
2009-02-01 12:56 ` erik quanstrom
2009-02-02 19:25 ` sqweek
2009-02-02 19:44 ` erik quanstrom
2009-02-02 19:49 ` Roman V. Shaposhnik
2009-02-02 21:22 ` John Barham
2009-02-02 21:27 ` erik quanstrom
2009-02-02 21:32 ` David Leimbach
2009-02-02 22:11 ` Roman V. Shaposhnik
2009-02-02 22:17 ` erik quanstrom
2009-02-02 22:30 ` Anthony Sorace
2009-02-02 22:44 ` erik quanstrom
2009-02-02 22:57 ` Anthony Sorace
2009-02-02 23:04 ` Bruce Ellis
2009-02-03 4:26 ` lucio
2009-02-03 4:43 ` Bruce Ellis
2009-02-03 6:38 ` ron minnich
2009-02-02 23:18 ` David Leimbach
2009-02-02 22:12 ` ron minnich
2009-02-02 22:14 ` erik quanstrom
2009-02-02 22:32 ` ron minnich
2009-02-02 22:34 ` erik quanstrom
2009-02-02 22:18 ` Roman V. Shaposhnik
2009-02-02 22:22 ` Francisco J Ballesteros
2009-02-02 22:30 ` Roman V. Shaposhnik
2009-02-03 10:55 ` Richard Miller
2009-02-03 16:03 ` ron minnich
2009-02-03 16:07 ` erik quanstrom [this message]
2009-02-03 16:48 ` ron minnich
2009-02-03 17:01 ` erik quanstrom
2009-02-02 22:07 ` Roman V. Shaposhnik
2009-02-01 7:31 ` [9fans] Dynamic loading et al (Was: Pegasus 2.6 is released) lucio
2009-02-01 17:26 ` ron minnich
2009-02-01 18:42 ` lucio
2009-02-01 20:14 ` ron minnich
2009-02-01 18:04 ` Dave Eckhardt
2009-02-01 18:39 ` lucio
2009-02-01 11:26 ` [9fans] Pegasus 2.6 is released Charles Forsyth
2009-02-01 11:56 ` lucio
2009-02-01 13:02 ` erik quanstrom
2009-02-02 17:38 ` John Barham
2009-02-02 17:48 ` ron minnich
2009-02-01 4:50 Kenji Arisawa
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=9895aa081bff6e53edfa01c398576e7c@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).