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@9fans.net>
Subject: Re: [9fans] /net different from sockets, but better?
Date: Sat,  7 Feb 2009 07:47:08 -0600	[thread overview]
Message-ID: <a4e6962a0902070547r76a7aa1bq1bf67d2ccd38f90d@mail.gmail.com> (raw)
In-Reply-To: <9511f83e0902061913t2ff2c26bvd446ffe7ed8c30a0@mail.gmail.com>

I may have some existing code based on npfs that you can use as a
base.  It has the basic semantics down, but had at least one bug and
was somewhat incomplete.  I'll dig around and see if I can find it -
it may be of some use as a reference, particularly for how to deal
with the clone file.

                  -eric

On Fri, Feb 6, 2009 at 9:13 PM, Rahul Murmuria <rahul.is.also@gmail.com> wrote:
> I am planning on porting the /net concept of Plan9 to Linux.
>
> My Plan:
> Use libfs[1] to write a synthetic filesystem in Linux, much like
> securityfs[2], or /proc. This libfs based code will make calls to the TCP/IP
> stack on the linux, and basically be an alternative to the Linux kernel
> sockets. As a result I will expose networking using /net, instead of POSIX
> to the applications.
>
> My Motivation:
> Glendix[3]
>
> My Question:
> I know that using /net instead of sockets is very different. But is it
> better? Specially from the networking side of things, not from application
> development point of view (which we have already established is simpler, by
> example).
>
> [1] http://lwn.net/Articles/57369/
> [2] http://lwn.net/Articles/153366/
> [3] http://glendix.org/   and   http://glendix.org/glendix_iwp9_2008.pdf
> and    http://www.osnews.com/story/20588/
>
> Regards,
>
> --
> Rahul Murmuria
>
>



  reply	other threads:[~2009-02-07 13:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-07  3:13 Rahul Murmuria
2009-02-07 13:47 ` Eric Van Hensbergen [this message]
2009-02-08 19:03   ` Rahul Murmuria
2009-02-08 18:46 ` J.R. Mauro

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=a4e6962a0902070547r76a7aa1bq1bf67d2ccd38f90d@mail.gmail.com \
    --to=ericvh@gmail.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).