From: Lucio De Re <lucio@proxima.alt.za>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] How would you go about implementing this in Plan9?
Date: Fri, 10 Dec 2010 12:01:58 +0200 [thread overview]
Message-ID: <20101210100158.GG4184@fangle.proxima.alt.za> (raw)
In-Reply-To: <AANLkTinxxeziFAdbDDJC1Zz0g9KdXU3tMJu4ekjE5F1=@mail.gmail.com>
On Fri, Dec 10, 2010 at 10:46:43AM +0100, hiro wrote:
>
> How much overhead are we talking about?
In a real-time environment, it's easiest to think of all overheads as
being bad, even though often they don't have any noticeable impact.
++L
next prev parent reply other threads:[~2010-12-10 10:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 9:34 Eugene Gorodinsky
2010-12-10 9:46 ` Lucio De Re
2010-12-10 9:58 ` hiro
2010-12-10 9:46 ` hiro
2010-12-10 10:01 ` Lucio De Re [this message]
2010-12-10 10:30 ` Charles Forsyth
2010-12-10 11:21 ` Eugene Gorodinsky
2010-12-11 1:43 ` Nathaniel W Filardo
2010-12-11 19:02 ` Eugene Gorodinsky
2010-12-10 15:52 ` David Leimbach
2010-12-10 20:01 ` Eugene Gorodinsky
2010-12-10 20:33 ` Federico G. Benavento
2010-12-11 19:01 ` Eugene Gorodinsky
2010-12-10 11:47 ` Federico G. Benavento
2010-12-10 13:23 ` erik quanstrom
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=20101210100158.GG4184@fangle.proxima.alt.za \
--to=lucio@proxima.alt.za \
--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).