From: Eunbyung Park <silverbottlep@gmail.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: cap and reservation functionality in the credit2 scheduler?
Date: Wed, 05 Oct 2011 20:08:28 +0900 [thread overview]
Message-ID: <4E8C3AAC.3070206@gmail.com> (raw)
In-Reply-To: <CAFLBxZac-6oHaKdeO_kYJ1Y0Fns9xWTt5tyd1BBx0DpvFPk1Dw@mail.gmail.com>
2011-10-05 오후 7:24, George Dunlap 쓴 글:
>> > From my humble point of view, probably additional timer may be required
>> to implement them because there isn't any periodic timer in the credit2
>> unlike the previous credit scheduler.
>>
>> what do you think about it?
> I'm not opposed in principle, but until I've seen the whole algorithm,
> I can't really comment. :-) Do you have an algorithm in mind?
Actually, I don't have any idea in mind yet.
however, I will try to devise a method to support them and make a patch.
So, If you can afford to review, I will appreciate it :)
And, I think that there are still some to-do lists for the credit2 and
xl tools needs to include credit2 support.
In addition, I found that adjusting dom0 weight have failed to work, but
except for the dom0, it worked well.
I found that this problem had been on xen-devel lists long time ago, but
it seems not to be solved yet.
I think this may be related with spinlock. When I remove the
vcpu_schedule_lock_irq() in csched_dom_cntl(), it worked well.
I'm not sure what is the real problem because I didn't completely
understand the mechanism about spinlocks in xen scheduler.
Any comments? or new thread needed?
--
Best Regards,
Eunbyung Park
next prev parent reply other threads:[~2011-10-05 11:08 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 [this message]
2011-10-06 13:57 ` George Dunlap
2011-10-08 12:59 ` Eunbyung Park
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=4E8C3AAC.3070206@gmail.com \
--to=silverbottlep@gmail.com \
--cc=George.Dunlap@eu.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.