From: yan cui <ccuiyyan@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] GSOC proposal for plan9
Date: Sat, 15 Mar 2014 20:17:22 -0400 [thread overview]
Message-ID: <CAAVq3rkSXYx0dDAL52bupYhUbxjfM_yEtcGb9kr8foigOyTfmA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1294 bytes --]
Dear all,
I have noticed the comments of Anthony Sorace and Quanstro in my GSOC
proposal. Thanks very much! Basically, there are three problems.
[1]. The timeline has the time of reading related documents and source
codes, but Anthony thinks it should be solved before the coding stage.
[Yan] I have removed the reading stage from the timeline and use the time
to write code and do some testing.
[2]. I did not add the considerations of testing and measurements.
[Yan] in the updated proposal, I add my idea of testing in the timeline
part.
Basically, I plan to write some code to stress the MCS lock in different
contention degree and see whether the MCS lock works as expected.
In addition, I plan to run some macro-benchmarks to test the performance of
MCS lock, and compared with the original TAS (test and set) implementation.
Quanstro, is that enough?
[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)?
Please provide comments, and I will update my proposal accordingly.
Best Wishes!
Yan
--
Think big; Dream impossible; Make it happen.
[-- Attachment #2: Type: text/html, Size: 1686 bytes --]
next reply other threads:[~2014-03-16 0:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-16 0:17 yan cui [this message]
2014-03-16 14:38 ` erik quanstrom
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=CAAVq3rkSXYx0dDAL52bupYhUbxjfM_yEtcGb9kr8foigOyTfmA@mail.gmail.com \
--to=ccuiyyan@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).