9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] replace p9sk1 with something better(9front)
Date: Thu,  2 Jul 2015 17:48:59 +0200	[thread overview]
Message-ID: <0e923b074630d564f0c12fe61f509d16@proxima.alt.za> (raw)
In-Reply-To: <CAOw7k5j4QrK-Upi4aEZKESgnbVqqSi38qztjN_Y3Q3hSTRTbsg@mail.gmail.com>

> I think that I'd avoid putting the negotiation and certificate stuff (as
> such) in the kernel device.

Speaking as an amateur, I'd be tempted to investigate pushing the Plan
9 paradigm further and see how hard it would be to fragment the kernel
into asymmetric portions.  To be more specific, something of the
magnitude of TLS, or USB, ought to be constructed as a subkernel or a
super-driver, able to run on GPUs in parallel with the CPU-based
kernel.  Thinking on my feet, I'd say the important factor would be
the establishment of boundaries between modules that can only be
crossed with the right type of credentials.

How much of this is old hat to those of us who are close to academia I
can't guess, but not having seen much mention of similar concepts, I'm
curious if anything in this vein is being explored at all (I'm sure
something that would appeal to me is, there are close to an infinite
number of monkeys out there typing on pretty close to an infinite
number of keyboards and an even more infinite number of CPUs).

Lucio.




  reply	other threads:[~2015-07-02 15:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-02 11:37 gracc
2015-07-02 12:12 ` steve
2015-07-02 12:30 ` Anthony Sorace
2015-07-02 12:57   ` Charles Forsyth
2015-07-02 13:14     ` Charles Forsyth
2015-07-02 15:48       ` lucio [this message]
2015-07-02 16:44       ` Skip Tavakkolian
2015-07-02 17:38         ` Charles Forsyth
2015-07-02 20:15       ` cinap_lenrek

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=0e923b074630d564f0c12fe61f509d16@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).