From: erik quanstrom <quanstro@quanstro.net>
To: ccuiyyan@gmail.com, 9fans@9fans.net
Subject: Re: [9fans] GSOC proposal for plan9
Date: Sun, 16 Mar 2014 10:38:15 -0400 [thread overview]
Message-ID: <c4f507c05e09757fa00f035d59600075@brasstown.quanstro.net> (raw)
In-Reply-To: <CAAVq3rkSXYx0dDAL52bupYhUbxjfM_yEtcGb9kr8foigOyTfmA@mail.gmail.com>
> [3]. Should avoid the patent issue of the K42 system.
> [Yan] For this problem, I do not have any idea right now. Do we need to
> propose a different solution (from K42's MCS lock), but solve the same
> problem (do not need to pass node data structure in the parameter)?
of course the simplist version of this is allocating Qnodes internally.
this can be done locklessly because held locks cannot switch Mach.
alternatively, since we *can* modify the definition of the the structure
Lock, MAXMACH Qnodes could be part of the lock.
i'm sure that you'll have good ideas on this, too.
- erik
prev parent reply other threads:[~2014-03-16 14:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-16 0:17 yan cui
2014-03-16 14:38 ` erik quanstrom [this message]
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=c4f507c05e09757fa00f035d59600075@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
--cc=ccuiyyan@gmail.com \
/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).