From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] 9p2010
Date: Thu, 23 Apr 2009 13:28:31 -0400 [thread overview]
Message-ID: <74397773b7238fd47d00b9a51fdbfd61@quanstro.net> (raw)
In-Reply-To: <df49a7370904231022g1ce3d3f9sf172b095898b9592@mail.gmail.com>
> as a starting point, i'd envisaged simply changing the existing
> system calls to do sequences.
>
[...]
>
> Sequence: adt {
> queue: fn(seq: self ref Sequence, m: Tmsg, tag: any);
> wait: fn(seq: self ref Sequence): (any, Tmsg, Rmsg);
> cont: fn(seq: self ref Sequence);
> flush: fn(seq: self ref Sequence);
> }
this is significantly more complicated than syscalls.
- erik
next prev parent reply other threads:[~2009-04-23 17:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 16:26 erik quanstrom
2009-04-23 17:22 ` roger peppe
2009-04-23 17:28 ` erik quanstrom [this message]
2009-04-23 17:38 ` David Leimbach
2009-04-23 17:31 ` Fco. J. Ballesteros
2009-04-23 17:53 ` roger peppe
2009-04-26 21:29 ` Roman V. Shaposhnik
2009-04-27 7:32 ` roger peppe
2009-04-23 17:55 ` Eric Van Hensbergen
2009-04-23 18:35 ` Steve Simon
2009-04-23 17:54 ` Gary Wright
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=74397773b7238fd47d00b9a51fdbfd61@quanstro.net \
--to=quanstro@quanstro.net \
--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).