linux-kernel - Re: [PATCH] sched/fair: Set se->vruntime directly in place

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAKohpokC5T8+iEiEbz1aoz0mgVXWULuBcVKp3KoQOxe7FfxZYg@mail.gmail.com>
Date:	Wed, 2 Jan 2013 11:14:23 +0530
From:	Viresh Kumar <viresh.kumar@...aro.org>
To:	mingo@...hat.com, peterz@...radead.org
Cc:	linaro-dev@...ts.linaro.org, patches@...aro.org,
	linux-kernel@...r.kernel.org,
	Viresh Kumar <viresh.kumar@...aro.org>
Subject: Re: [PATCH] sched/fair: Set se->vruntime directly in place_entity()

On 8 November 2012 13:33, Viresh Kumar <viresh.kumar@...aro.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@...aro.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!!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/