From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] running plan9 : an ideal setup?
Date: Fri, 21 Nov 2014 09:31:19 -0800 [thread overview]
Message-ID: <0841E3F3-400C-4E19-811F-37B0595006BD@bitblocks.com> (raw)
In-Reply-To: <418789bb5bc4501ab70366014c15b965@lilly.quanstro.net>
This paper is well worth reading:
http://groups.csail.mit.edu/ana/Publications/PubPDFs/1988Analysis%20TCP%20Processing%20Overhead.pdf
While the traditional BSD implementation uses mbufs that complicate things, actual tcp processing can be done quite cheaply.
> On Nov 21, 2014, at 6:34 AM, erik quanstrom <quanstro@quanstro.net> wrote:
>
>> On Thu Nov 20 13:44:04 EST 2014, a@9srv.net wrote:
>> Both. I agree with what you're saying about the computers, but I was thinking of the fact that the wire speed is fast enough in most cases that the tcp/ip overhead doesn't impact things noticeably for most uses. There are outliers in both cases, of course.
>
> this is not correct. tcp doesn't help at all when the wire is fast (short, fat). it's the classic tradeoff of cpu
> for (networking) performance. the wire being fast enough is an argument against using tcp,
> not for it.
>
> so really, it's the gobs of cpu we currently have that make tcp not an issue, not the gobs of bandwidth.
>
> - erik
>
next prev parent reply other threads:[~2014-11-21 17:31 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 13:29 Mayuresh Kathe
2014-11-18 13:53 ` dante
2014-11-18 14:11 ` Richard Miller
2014-11-18 14:28 ` dante
2014-11-27 20:57 ` Dante
2014-11-28 6:10 ` erik quanstrom
2014-11-28 6:54 ` David du Colombier
2014-11-28 8:42 ` Dante
2014-11-28 9:12 ` Mats Olsson
2014-11-28 9:18 ` Dante
2014-11-28 9:17 ` Richard Miller
2014-11-28 9:26 ` Dante
2014-11-28 13:20 ` erik quanstrom
2014-11-28 13:45 ` David du Colombier
2014-11-18 15:42 ` Kurt H Maier
2014-11-18 16:14 ` dante
2014-11-18 17:02 ` Aram Hăvărneanu
2014-11-18 20:29 ` Richard Miller
2014-11-18 21:28 ` Mats Olsson
2014-11-18 22:09 ` dante
2014-11-19 8:56 ` Mats Olsson
2014-11-26 17:16 ` Mats Olsson
2014-11-26 17:41 ` Dante
2014-11-26 17:56 ` Mats Olsson
2014-11-26 18:16 ` Mats Olsson
2014-11-26 18:41 ` Dante
2014-11-18 22:11 ` Skip Tavakkolian
2014-11-18 22:23 ` Steve Simon
2014-11-19 1:57 ` erik quanstrom
2014-11-19 5:36 ` Skip Tavakkolian
2014-11-19 5:59 ` lucio
2014-11-19 14:36 ` erik quanstrom
2014-11-19 15:34 ` Aram Hăvărneanu
2014-11-20 6:02 ` Anthony Sorace
2014-11-20 14:37 ` erik quanstrom
2014-11-20 18:43 ` Anthony Sorace
2014-11-21 14:34 ` erik quanstrom
2014-11-21 14:44 ` Anthony Sorace
2014-11-21 17:31 ` Bakul Shah [this message]
2014-11-22 18:06 ` erik quanstrom
2014-11-25 6:59 ` Bakul Shah
2014-11-25 11:10 ` erik quanstrom
2014-11-25 11:14 ` erik quanstrom
2014-11-25 13:52 ` Anthony Sorace
2014-11-25 14:26 ` erik quanstrom
2014-11-19 14:33 ` erik quanstrom
2014-11-19 20:05 ` Bakul Shah
2014-11-19 20:40 ` Tom Ivar Helbekkmo
2014-11-21 6:34 ` Harri Haataja
2014-11-19 2:04 ` erik quanstrom
2014-11-19 3:50 ` lucio
2014-11-19 9:40 ` Steve Simon
2014-11-19 9:50 ` dante
2014-11-19 10:18 ` Steve Simon
2014-11-19 10:27 ` dante
2014-11-19 18:55 ` Quintile
2014-11-19 10:36 ` lucio
2014-11-20 6:05 ` Anthony Sorace
2014-11-20 6:13 ` lucio
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=0841E3F3-400C-4E19-811F-37B0595006BD@bitblocks.com \
--to=bakul@bitblocks.com \
--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).