From: mischief@offblast.org (Nick Owens)
Subject: [9fans] Why is the tcp/ip stack of plan9 implemented in kernel?
Date: Sat, 27 Jan 2018 03:06:07 -0800 [thread overview]
Message-ID: <CAH_zEu4WMuqsTBPUKm+eF=M2tFgSJXJN2uwW3sj+ZwU6rY+j3w@mail.gmail.com> (raw)
In-Reply-To: <59023bc9d534255352961e36cd7a3bec@quintile.net>
it used to be in userspace, but i believe it was moved to the kernel
for performance reasons.
the remaining evidence of the ip stack in the kernel lives on in (at
least) 9front's sysproc.c, where sysexec raises the process priority
if the program is "/ip", which i assume would be the tcp/ip stack
binary embedded in the kernel image's devroot (not the paqfs):
/*
* '/' processes are higher priority (hack to make /ip more responsive).
*/
if(devtab[tc->type]->dc == L'/')
up->basepri = PriRoot;
On Sat, Jan 27, 2018 at 1:45 AM, Steve Simon <steve at quintile.net> wrote:
> in early versions of plan9 the tcp/ip stack in Streams, inherited (I assume) from V10.
>
> This turned out not to be as clean nor as efficent as hoped and this was dropped
> for a more traditional implementation in later releases. Maybe the bad experiences
> of poor performance informed the decision for an in-kernel implementation?
>
> -Steve
>
prev parent reply other threads:[~2018-01-27 11:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-27 7:04 lchg
2018-01-27 9:35 ` FJ Ballesteros
2018-01-27 9:45 ` Steve Simon
2018-01-27 11:06 ` Nick Owens [this message]
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='CAH_zEu4WMuqsTBPUKm+eF=M2tFgSJXJN2uwW3sj+ZwU6rY+j3w@mail.gmail.com' \
--to=mischief@offblast.org \
/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).