[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RFC PATCH v1 3/6] sched, credit2: improve scheduler fairness


  • To: "jgross@xxxxxxxx" <jgross@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • From: Volodymyr Babchuk <Volodymyr_Babchuk@xxxxxxxx>
  • Date: Fri, 12 Jun 2020 11:38:25 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=epam.com; dmarc=pass action=none header.from=epam.com; dkim=pass header.d=epam.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=nKr01J6bycECPR64sbz8JtTVBqlGyFTxjcHpxmtJoH8=; b=DxlFi2xzPeCDA44Czx2OkpTPvqlaVoXUtcHp45jmlEuN6Q7aH8aWKVCsvjCJbgBC4OHAOyn3k0f1NUl5xM9IyB1X/JsU7NGfYhKHZ8RmXytz2raGmB5vJ7aRE8ceSeZrkcUX71z2I7mHMuIiWCmPKTkKl1jeAl0JatTiQKxN0pONSizgKqXAWYE/pXrfjtqJ5ezyd9YKyVfGipBKxBWgYRZCW2urYL0NwzVTvIClNahQiK0yN8hzKSfJKsogRVVty2PocmhpGcrEGV1I3V0zpzfnxts7M+qyAVpU7FTX39gZMtJo6v82y9z1FEoshj5iIqGvLKIsC29FeGxsTayiNA==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ahvu33HQTfnRNpCyULoCeK1K10X5cHGey7EzQpPvIlA0iQ7Law5+Ud9IfBreBRq6j8r/vBKmiviF/lU0Ow1nIG7yQ3LMlL2+ZTBSye+pc4xu5WBVCL7M1Da7ewjf56Vl7gm06LkRiSliPRF0KCHP6jcbZA19GxT1qm2tk7otwWHGQk//VQjh0Akt1GoSVurcZQlMxm74iguMMXr55skb/3p1MCZtuJdMcMwQpTBE0DPEBbEozhov0+95qo7nkfa8gT40iqbhNL4I0qVJNjG8V4Z/ucHF9mHyBQ8jvpRLCdSRUEdSIarjGv7U+CsWnFvIsCQywsM7WT9djk2v+Hz3Qw==
  • Authentication-results: suse.com; dkim=none (message not signed) header.d=none;suse.com; dmarc=none action=none header.from=epam.com;
  • Cc: "george.dunlap@xxxxxxxxxx" <george.dunlap@xxxxxxxxxx>, "dfaggioli@xxxxxxxx" <dfaggioli@xxxxxxxx>
  • Delivery-date: Fri, 12 Jun 2020 11:38:31 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
  • Thread-index: AQHWQE+TBfX1MPdkGkC6vJ7ur/uY5KjUaaaAgABxsoA=
  • Thread-topic: [RFC PATCH v1 3/6] sched, credit2: improve scheduler fairness

On Fri, 2020-06-12 at 06:51 +0200, Jürgen Groß wrote:
> On 12.06.20 02:22, Volodymyr Babchuk wrote:
> > Now we can make corrections for scheduling unit run time, based on
> > data gathered in previous patches. This includes time spent in IRQ
> > handlers and time spent for hypervisor housekeeping tasks. Those time
> > spans needs to be deduced from a total run time.
> > 
> > This patch adds sched_get_time_correction() function which returns
> > time correction value. This value should be subtracted by a scheduler
> > implementation from a total vCPU/shced_unit run time.
> > 
> > TODO: Make the corresponding changes to all other schedulers.
> > 
> > Signed-off-by: Volodymyr Babchuk <volodymyr_babchuk@xxxxxxxx>
> > ---
> >   xen/common/sched/core.c    | 23 +++++++++++++++++++++++
> >   xen/common/sched/credit2.c |  2 +-
> >   xen/common/sched/private.h | 10 ++++++++++
> >   3 files changed, 34 insertions(+), 1 deletion(-)
> > 
> > diff --git a/xen/common/sched/core.c b/xen/common/sched/core.c
> > index d597811fef..a7294ff5c3 100644
> > --- a/xen/common/sched/core.c
> > +++ b/xen/common/sched/core.c
> > @@ -974,6 +974,29 @@ void vcpu_end_hyp_task(struct vcpu *v)
> >   #ifndef NDEBUG
> >       v->in_hyp_task = false;
> >   #endif
> > +
> > +s_time_t sched_get_time_correction(struct sched_unit *u)
> > +{
> > +    unsigned long flags;
> > +    int irq, hyp;
> 
> Using "irq" for a time value is misleading IMO.

Yes, you are right. I'll rename this variables to irq_time and
hyp_time. 

> > +
> > +    while ( true )
> > +    {
> > +        irq = atomic_read(&u->irq_time);
> > +        if ( likely( irq == atomic_cmpxchg(&u->irq_time, irq, 0)) )
> > +            break;
> > +    }
> 
> Just use atomic_xchg()?

Thanks. I somehow missed this macro.

> > +
> > +    while ( true )
> > +    {
> > +        hyp = atomic_read(&u->hyp_time);
> > +        if ( likely( hyp == atomic_cmpxchg(&u->hyp_time, hyp, 0)) )
> > +            break;
> > +    }
> > +
> > +    return irq + hyp;
> 
> Ah, I didn't look into this patch until now.
> 
> You can replace my comments about overflow of an int for patches 1 and 2
> with:
> 
>    Please modify the comment about not overflowing hinting to the value
>    being reset when making scheduling decisions.

Will do.

> And this (of course) needs to be handled in all other schedulers, too.
> 

Yes, the plan is to call this function in all schedulers. I skipped
this in RFC, because I wanted to discuss the general approch. I'll add
support for all other schedulers in the next version.

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.