From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eunbyung Park Subject: Re: cap and reservation functionality in the credit2 scheduler? Date: Sat, 08 Oct 2011 21:59:34 +0900 Message-ID: <4E904936.5090102@gmail.com> References: <4E8BE083.3080000@gmail.com> <4E8C3AAC.3070206@gmail.com> <1317909439.15843.33.camel@elijah> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1317909439.15843.33.camel@elijah> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: George Dunlap Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org > 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