From: Bhanu Nagendra Pisupati <bpisupat@cs.indiana.edu>
To: 9fans@9fans.net
Subject: [9fans] critique of sockets API
Date: Tue, 9 Jun 2009 14:49:44 -0400 [thread overview]
Message-ID: <Pine.LNX.4.64.0906081807350.385@tank.cs.indiana.edu> (raw)
Interesting read:
http://cacm.acm.org/magazines/2009/6/28495-whither-sockets/fulltext
If I am right, the filesystem based networking interface offered by Plan 9
has the three limitations discussed here:
* performance overhead: app requesting data from a socket typically needs
to perform 2 system calls (select/read or alt/read)
* lack of an "kernel up-call API": which allows the kernel to inform an
app each time network data is available
* hard to implement "multi homing" with support for multiple network
interfaces
Any thoughts/comments?
Thanks,
-Bhanu
next reply other threads:[~2009-06-09 18:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 18:49 Bhanu Nagendra Pisupati [this message]
2009-06-09 18:59 ` erik quanstrom
2009-06-09 22:11 ` Russ Cox
[not found] <mailman.998.1244574121.1513.9fans@9fans.net>
2009-06-09 23:20 ` Bhanu Nagendra Pisupati
2009-06-09 23:24 ` J.R. Mauro
2009-06-09 23:33 ` Devon H. O'Dell
2009-06-10 3:33 ` Gary Wright
2009-06-10 0:07 ` erik quanstrom
2009-06-10 0:34 ` erik quanstrom
2009-06-11 7:07 ` Eris Discordia
[not found] <mailman.1007.1244590421.1513.9fans@9fans.net>
2009-06-10 22:50 ` Bhanu Nagendra Pisupati
2009-06-11 12:34 ` erik quanstrom
[not found] <mailman.1.1244635201.19660.9fans@9fans.net>
2009-06-10 23:46 ` Bhanu Nagendra Pisupati
2009-06-11 12:16 erik quanstrom
[not found] <b0a72b5826eb44300d3603f585859910@quanstro.net>
2009-06-11 14:54 ` Eris Discordia
2009-06-11 18:24 ` erik quanstrom
2009-06-11 21:21 ` Eris Discordia
2009-06-11 23:41 ` erik quanstrom
2009-06-12 4:32 ` Paul Lalonde
2009-06-12 7:19 ` Eris Discordia
[not found] ` <D9FE8C51EE2D568C05E555DD@192.168.1.2>
2009-06-11 23:34 ` Devon H. O'Dell
2009-06-12 7:21 ` Eris Discordia
[not found] <mailman.1.1244808001.26495.9fans@9fans.net>
2009-06-13 1:39 ` Bhanu Nagendra Pisupati
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=Pine.LNX.4.64.0906081807350.385@tank.cs.indiana.edu \
--to=bpisupat@cs.indiana.edu \
--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).