[PATCH] Enable per-VCPU parameter settings for RTDS scheduler

[PATCH] Enable per-VCPU parameter settings for RTDS scheduler

[Chong Li]

Hi,

I sent out a new version of our patchset (enable per-VCPU parameter
settings for RTDS scheduler) two weeks ago. Can I get some feedbacks
and comments about it? I'm waiting for these so that I can work out
the next version soon.

Best!
Chong

-- 
Chong Li
Department of Computer Science and Engineering
Washington University in St.louis

Re: [PATCH] Enable per-VCPU parameter settings for RTDS scheduler

[Jan Beulich]

>>> On 24.07.15 at 17:39, <lichong659@gmail.com> wrote:
> I sent out a new version of our patchset (enable per-VCPU parameter
> settings for RTDS scheduler) two weeks ago. Can I get some feedbacks
> and comments about it? I'm waiting for these so that I can work out
> the next version soon.

First of all, such a ping would better be sent as a reply to the original
submission.

And then, if you mean
http://lists.xenproject.org/archives/html/xen-devel/2015-07/msg02240.html
then I replied (without any further reaction) in
http://lists.xenproject.org/archives/html/xen-devel/2015-07/msg02334.html
and considering the feature freeze you probably should be a little
more patient (e.g. ping when the development tree re-opened).

Jan

Re: [PATCH] Enable per-VCPU parameter settings for RTDS scheduler

[Chong Li]

On Fri, Jul 24, 2015 at 10:54 AM, Jan Beulich <JBeulich@suse.com> wrote:
>>>> On 24.07.15 at 17:39, <lichong659@gmail.com> wrote:
>> I sent out a new version of our patchset (enable per-VCPU parameter
>> settings for RTDS scheduler) two weeks ago. Can I get some feedbacks
>> and comments about it? I'm waiting for these so that I can work out
>> the next version soon.
>
> First of all, such a ping would better be sent as a reply to the original
> submission.
>
> And then, if you mean
> http://lists.xenproject.org/archives/html/xen-devel/2015-07/msg02240.html

Yes. That's my original submission.

> then I replied (without any further reaction) in
> http://lists.xenproject.org/archives/html/xen-devel/2015-07/msg02334.html
> and considering the feature freeze you probably should be a little
> more patient (e.g. ping when the development tree re-opened).

Sure, thanks for your reply.
>
> Jan
>



-- 
Chong Li
Department of Computer Science and Engineering
Washington University in St.louis

Re: [PATCH] Enable per-VCPU parameter settings for RTDS scheduler

[Ian Campbell]

On Fri, 2015-07-24 at 09:54 -0600, Jan Beulich wrote:
> considering the feature freeze you probably should be a little
> more patient (e.g. ping when the development tree re-opened).

I don't think all 4.7 development needs to come to a halt just because we
have frozen for 4.6. Although 4.6 should be the priority, not all devs and
maintainers will be spending 100% of their time on 4.6 related stuff). 

So while maybe waiting a bit longer than usual would be good advice I don't
think waiting for the development tree to reopen is correct.

A series can still be reviewed, revised and reposted during the freeze
until they are in a state to go in, at which point they may need to be
parked or queued until the tree reopens.

Ian.

Re: [PATCH] Enable per-VCPU parameter settings for RTDS scheduler

[Jan Beulich]

>>> On 24.07.15 at 18:09, <ian.campbell@citrix.com> wrote:
> On Fri, 2015-07-24 at 09:54 -0600, Jan Beulich wrote:
>> considering the feature freeze you probably should be a little
>> more patient (e.g. ping when the development tree re-opened).
> 
> I don't think all 4.7 development needs to come to a halt just because we
> have frozen for 4.6. Although 4.6 should be the priority, not all devs and
> maintainers will be spending 100% of their time on 4.6 related stuff). 
> 
> So while maybe waiting a bit longer than usual would be good advice I don't
> think waiting for the development tree to reopen is correct.
> 
> A series can still be reviewed, revised and reposted during the freeze
> until they are in a state to go in, at which point they may need to be
> parked or queued until the tree reopens.

Which I agree with, and which I don't think my reply excluded.
Anyway - I was mainly puzzled by the ping because I had replied,
without myself getting a reply...

Jan