From: Bakul Shah <bakul@bitblocks.com>
To: ron minnich <rminnich@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Unix APIs: elegant or not?
Date: Thu, 01 Nov 2018 22:24:27 -0700 [thread overview]
Message-ID: <20181102052434.93EC6156E40C@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Thu, 01 Nov 2018 09:48:38 -0700." <CAP6exY+ZxHC3H=jUt0G1kGPJQdMUid40Lt4aDkf80tevC9K1dg@mail.gmail.com>
On Thu, 01 Nov 2018 09:48:38 -0700 ron minnich <rminnich@gmail.com> wrote:
>
> On Thu, Nov 1, 2018 at 9:44 AM Warner Losh <imp@bsdimp.com> wrote:
> >
> > There's another school of thought too that says the kernel has no business
> > parsing strings with all the security implications of doing so...
Which is more a function of C. A proper string type might've
helped. I would argue it is *easier* to debug string based
stuff than all those ioctls using magic numbers replaced with
#defines.
> And, further, that network architecture I referenced is much less efficient
> than the BSD model -- 5 system calls per accept! so that was starting to
> hit us here on the Akaros project, since we imported the entire Plan 9
> network stack into akaros, along with the drivers. Linux left us in the
> dust on network connections/second. We were going to change it had Akaros
> continued.
What sort of changes were you contemplating?
I view(ed) 9p more as a prototype.
next prev parent reply other threads:[~2018-11-02 6:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 4:38 Warren Toomey
2018-10-31 15:47 ` Paul Winalski
2018-10-31 17:22 ` Clem Cole
2018-10-31 19:33 ` Lawrence Stewart
2018-10-31 20:57 ` G. Branden Robinson
2018-10-31 21:31 ` Dave Horsfall
2018-11-01 7:42 ` Pierre DAVID
2018-11-01 10:20 ` Dave Horsfall
2018-11-01 12:57 ` Clem Cole
2018-11-01 14:19 ` ron minnich
2018-11-01 14:41 ` Clem Cole
2018-11-01 16:43 ` Warner Losh
2018-11-01 16:48 ` ron minnich
2018-11-01 16:56 ` Warner Losh
2018-11-02 5:24 ` Bakul Shah [this message]
2018-11-04 10:53 ` Chris Hanson
2018-11-04 15:34 ` ron minnich
2018-11-04 17:06 ` Warner Losh
2018-11-04 20:00 ` ron minnich
2018-11-04 18:52 ` Bakul Shah
2018-11-04 10:49 ` Chris Hanson
2018-11-04 12:28 ` arnold
2018-11-04 21:34 ` Chris Hanson
2018-11-05 14:11 ` Donald ODona
2018-11-04 13:35 ` Warner Losh
2018-11-04 19:47 ` Dave Horsfall
2018-11-01 15:39 Noel Chiappa
2018-11-04 22:29 Theodore Y. Ts'o
2018-11-04 22:37 Noel Chiappa
2018-11-05 4:04 ` Dave Horsfall
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=20181102052434.93EC6156E40C@mail.bitblocks.com \
--to=bakul@bitblocks.com \
--cc=rminnich@gmail.com \
--cc=tuhs@tuhs.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).