From: yan cui <ccuiyyan@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] GSOC 2014 proposal for Plan 9
Date: Sun, 9 Mar 2014 16:42:05 -0400 [thread overview]
Message-ID: <CAAVq3rn+wgHNKitvxXZaCP0paUai3pQdsXRDxuwVcqOO0Z09CA@mail.gmail.com> (raw)
In-Reply-To: <1955b997f424ec1e9d2021d52e43ece3@mikro.quanstro.net>
[-- Attachment #1: Type: text/plain, Size: 2022 bytes --]
Erik, thanks for your reply! I will read the document carefully and submit
an application.
Best Wishes!
Yan
2014-03-09 16:30 GMT-04:00 erik quanstrom <quanstro@quanstro.net>:
> On Sun Mar 9 15:32:48 EDT 2014, ccuiyyan@gmail.com wrote:
>
> > Dear All,
> >
> > I am a student of Columbia university(Yan Cui) and want to
> > contribute to
> > plan 9 in google summer code. I am interested in one idea posted on
> > the idea list, which is titled "MCS locks (i.e. queueing locks) for
> > the kernel with a compatable calling interface to
> > *lock*(9)<http://plan9.bell-labs.com/magic/man2html/9/lock>".
> > Actually, my research direction is operating system scalability on
> > multicore systems and knows kinds of synchronization methods very well
> > including Linux kernel ticket lock, MCS lock, CLH lock, etc. For MCS
> > lock, I have done many experiments (such as replacing the Linux kernel
> > spin lock with MCS lock) and made improvements to it. I think I have
> > all backgrounds and experiences required. I believe I can complete
> > the task in time. Wonder to know can I join you in the Plan 9
> > development?
>
> excellent! i think you will find that plan 9 lends itself to this
> sort of work. you are certainly welcome at any time to join plan 9
> development.
>
> the key here is to work out how to keep the existing lock api.
> this is described here: http://www.9atom.org/magic/man2html/9/lock
> i've prototyped this in user space, but did not get any further.
>
> as for gsoc, please do submit an application. there does happen to
> be another student interested in MCS locks. so we may need to
> work out something to avoid having to pick between two good
> applications. but i am confident that we can figure this out as
> things move forward.
>
> if you have any more questsion, please ask the list, or contact
> me off list via email or g+.
>
> cheers!
>
> - erik
>
>
--
Think big; Dream impossible; Make it happen.
[-- Attachment #2: Type: text/html, Size: 2830 bytes --]
next prev parent reply other threads:[~2014-03-09 20:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-09 19:31 yan cui
2014-03-09 20:30 ` erik quanstrom
2014-03-09 20:42 ` yan cui [this message]
2014-03-12 3:06 ` yan cui
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=CAAVq3rn+wgHNKitvxXZaCP0paUai3pQdsXRDxuwVcqOO0Z09CA@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).