linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: mingo@redhat.com, peterz@infradead.org
Cc: linaro-dev@lists.linaro.org, patches@linaro.org,
	linux-kernel@vger.kernel.org,
	Viresh Kumar <viresh.kumar@linaro.org>
Subject: Re: [PATCH] sched/fair: Set se->vruntime directly in place_entity()
Date: Wed, 2 Jan 2013 11:14:23 +0530	[thread overview]
Message-ID: <CAKohpokC5T8+iEiEbz1aoz0mgVXWULuBcVKp3KoQOxe7FfxZYg@mail.gmail.com> (raw)
In-Reply-To: <ae59db1945518d6f6250920d46eb1f1a9cc0024e.1352361704.git.viresh.kumar@linaro.org>

On 8 November 2012 13:33, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> We are first storing the new vruntime in a variable and then storing it in
> se->vruntime. Simply update se->vruntime directly.
>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---
>  kernel/sched/fair.c | 4 +---
>  1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index a319d56c..820a2f1 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -1454,9 +1454,7 @@ place_entity(struct cfs_rq *cfs_rq, struct sched_entity *se, int initial)
>         }
>
>         /* ensure we never gain time by being placed backwards. */
> -       vruntime = max_vruntime(se->vruntime, vruntime);
> -
> -       se->vruntime = vruntime;
> +       se->vruntime = max_vruntime(se->vruntime, vruntime);
>  }

Ping!!

  reply	other threads:[~2013-01-02  5:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-08  8:03 [PATCH] sched/fair: Set se->vruntime directly in place_entity() Viresh Kumar
2013-01-02  5:44 ` Viresh Kumar [this message]
2013-01-24 20:44 ` [tip:sched/core] sched/fair: Set se-> vruntime " tip-bot for Viresh Kumar

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=CAKohpokC5T8+iEiEbz1aoz0mgVXWULuBcVKp3KoQOxe7FfxZYg@mail.gmail.com \
    --to=viresh.kumar@linaro.org \
    --cc=linaro-dev@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=patches@linaro.org \
    --cc=peterz@infradead.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).