From: Eunbyung Park <silverbottlep@gmail.com>
To: George Dunlap <george.dunlap@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: cap and reservation functionality in the credit2 scheduler?
Date: Sat, 08 Oct 2011 21:59:34 +0900 [thread overview]
Message-ID: <4E904936.5090102@gmail.com> (raw)
In-Reply-To: <1317909439.15843.33.camel@elijah>
> I hope that doesn't sound too harsh, but the fact is that the scheduler
> is probably one of the most deceptively simple parts of the Xen code.
> It requires a lot of expertise to know even how to avoid race conditions
> and deadlock, not to mention making a simple algorithm which has the
> desired effects without undesirable side effects. (The shadow code is
> probably more complicated, for example, but it *looks* more complicated,
> so people don't end up in over their head.) I wouldn't be doing either
> you or me a favor by encouraging you to work on something past your
> capability level.
It was too harsh comments. just kidding~~:)
Anyway, nowadays, I am working on the project which is related with the
xen scheduler. Actually, I do not have enough expertise yet, however, I
am very interested and excited at the xen source code and I am a little
bit more getting used to it. I hope that I would completely understand
the all of the mechanisms soon and hack the xen source.
Thanks, george.
--
Best Regards,
Eunbyung Park
prev parent reply other threads:[~2011-10-08 12:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 4:43 cap and reservation functionality in the credit2 scheduler? Eunbyung Park
2011-10-05 10:24 ` George Dunlap
2011-10-05 11:08 ` Eunbyung Park
2011-10-06 13:57 ` George Dunlap
2011-10-08 12:59 ` Eunbyung Park [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=4E904936.5090102@gmail.com \
--to=silverbottlep@gmail.com \
--cc=george.dunlap@citrix.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.