9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Enrico Weigelt <weigelt@metux.de>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Binary format
Date: Wed, 17 Feb 2010 20:02:22 +0100	[thread overview]
Message-ID: <20100217190221.GD17100@nibiru.local> (raw)
In-Reply-To: <3e1162e61002171034x765459b4v22b7755e47bbe7ff@mail.gmail.com>

* David Leimbach <leimy2k@gmail.com> wrote:

> No I'm not saying replace all library code with filesystems.  I don't know
> why you'd want an RPC interface to an XML parser :-).

You need to implement an RPC protocol for that. And most likely you
want to get the parsed content into some convenient in-memory structure.
This probably ends up at an similar code size than the parser itself
would be, plus you have the communication overhead.

> Libraries may not always be more efficient than services.  Imagine if Intel
> released their 48 core machine today, how would your system utilize those
> cores?  Sequential programming optimizations don't (always) work in the
> parallel world, and in a lot of cases you actually want to work redundantly
> across multiple processes in order to avoid communication overheads in a
> well optimized parallel algorithm.

Wait, you cheated! You simply assumed that the application is question
can be parallized. In our XML example, there's great chance that the
application has to wait for the parser anyways, so the extra cpus/cores
would help much here. This perhaps would make sense if the file is
quite huge, the application is accessing the xml nodes quite sequentally
and does a lot of things in between. (coroutines would be fine here ;))


Unfortunately, this all is quite academical - I cant just take Plan9
for daily business uses, I just dont have the luxury of resources to
implement all the missing stuff on green land. :(
So I just can try to learn from it and take the concepts into "realworld"
step by step.


cu
--
----------------------------------------------------------------------
 Enrico Weigelt, metux IT service -- http://www.metux.de/

 phone:  +49 36207 519931  email: weigelt@metux.de
 mobile: +49 174 7066481   icq:   210169427         skype: nekrad666
----------------------------------------------------------------------
 Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------



  reply	other threads:[~2010-02-17 19:02 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-17 13:31 Enrico Weigelt
2010-02-17  8:50 ` Jacob Todd
2010-02-17 13:58   ` Enrico Weigelt
2010-02-17 14:01     ` erik quanstrom
2010-02-17 14:06 ` Gorka Guardiola
2010-02-17 14:13   ` David Leimbach
2010-02-17 14:33   ` Enrico Weigelt
2010-02-17 14:55     ` Steve Simon
2010-02-17 15:04       ` Enrico Weigelt
2010-02-17 15:29         ` erik quanstrom
2010-02-17 15:48         ` blstuart
2010-02-17 17:54           ` lucio
2010-02-17 18:37         ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2010-02-17 19:00         ` Nick LaForge
2010-02-18 15:08         ` Patrick Kelly
2010-02-17 15:58       ` David Leimbach
2010-02-17 16:14       ` Stuart Morrow
2010-02-17 16:28         ` David Leimbach
2010-02-17 18:21           ` Enrico Weigelt
2010-02-17 18:34             ` David Leimbach
2010-02-17 19:02               ` Enrico Weigelt [this message]
2010-02-17 19:35                 ` Enrico Weigelt
2010-02-17 18:38             ` Corey Thomasson
2010-02-18 15:16             ` Patrick Kelly
2010-02-17 15:13     ` Robert Raschke
2010-02-17 21:32     ` Jacob Todd
2010-02-17 21:26   ` Nathaniel W Filardo
2010-02-17 23:16     ` EBo
2010-02-17 23:22       ` David Leimbach
2010-02-17 14:38 ` blstuart
2010-02-17 14:58   ` Enrico Weigelt
2010-02-17 15:25     ` blstuart

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=20100217190221.GD17100@nibiru.local \
    --to=weigelt@metux.de \
    --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).