9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Eric Van Hensbergen" <ericvh@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: what about microkernel?
Date: Mon,  8 Oct 2007 14:14:06 -0500	[thread overview]
Message-ID: <a4e6962a0710081214x6c514068pdc75667d6b507efc@mail.gmail.com> (raw)
In-Reply-To: <fd560e48da8617ef67bc97347de7c71b@coraid.com>

On 10/8/07, erik quanstrom <quanstro@coraid.com> wrote:
> > I've been thinking a lot about this, particularly as we've been diving
> > deep into tracing performance of our network paths as part of the Blue
> > Gene work.  As of our preliminary results, it would seem that Plan 9
> > attempts to take the most general approach to things with an emphasis
> > on keeping everything simple.  Unfortunately we end up paying a heavy
> > price in raw performance (at least in the networking case).
>
> i have found plan 9 ip networking does not fair well pushing ip networking
> at 10gbps, especially tcp, and especially with standard ethernet frames.
>
> i didn't spend enough time this spring with the tcp stack to understand what
> it's doing, but i got the impression that it could make the simple case
> of receiving packets in order simplier at the expence of misorderd packets.
>
> fwiw, we get much greater performance pushing AoE.  so i don't think
> that network queues themselves are the problem.
>

I think most of the issues we are facing are due to somewhat difficult
esoteric network interfaces combined with a single 700 MHz simple
embedded in-order processor.  That being said however, any advantages
we can get on the relatively slow hardware should benefit the
efficiency (if not the latency and performance) of the faster
platforms.  Even if we can push peak on our platform it won't help us
if we are chewing up cpu cycles that we need for computation.

             -eric


  reply	other threads:[~2007-10-08 19:14 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-06 13:25 [9fans] " Andrew Wingorodov
2007-10-06 16:07 ` Lorenzo Fernando Bivens de la Fuente
2007-10-06 16:08 ` johnny
2007-10-06 16:26 ` Charles Forsyth
2007-10-06 20:24   ` [9fans] " Andrew Wingorodov
2007-10-06 20:50     ` Charles Forsyth
2007-10-07 16:18       ` David Leimbach
2007-10-07 16:30         ` ron minnich
2007-10-07 18:05           ` erik quanstrom
2007-10-07 20:28           ` David Leimbach
2007-10-07 20:49             ` Francisco J Ballesteros
2007-10-08 13:20               ` LiteStar numnums
2007-10-08 13:27                 ` Charles Forsyth
2007-10-08 14:50                 ` erik quanstrom
2007-10-08 15:58                   ` Eric Van Hensbergen
2007-10-08 16:01                     ` Francisco J Ballesteros
2007-10-08 17:16                     ` erik quanstrom
2007-10-08 19:14                       ` Eric Van Hensbergen [this message]
2007-10-08 19:53                         ` Charles Forsyth
2007-10-08 20:18                           ` Eric Van Hensbergen
2007-10-10 18:26                             ` David Leimbach
2007-10-10 20:42                               ` ron minnich
2007-10-10 21:38                                 ` David Leimbach
2007-10-08 17:46                     ` Charles Forsyth
2007-10-08 18:39                       ` David Leimbach
2007-10-08 19:11                       ` Eric Van Hensbergen
2007-10-08 18:34                     ` David Leimbach
2007-10-07 16:31         ` LiteStar numnums
2007-10-07 18:36         ` Andrew Wingorodov
2007-10-07 18:54           ` LiteStar numnums
2007-10-07 20:20           ` David Leimbach
2007-10-13  7:08 ` Andrew Wingorodov

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=a4e6962a0710081214x6c514068pdc75667d6b507efc@mail.gmail.com \
    --to=ericvh@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).