All of lore.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Hillf Danton <hillf.zj@alibaba-inc.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] BFS CPU scheduler v0.450 with SMT nice support for linux-3.16
Date: Mon, 8 Dec 2014 07:26:09 +1100	[thread overview]
Message-ID: <CABqErrEakrJN800zdCMJvmFk0j2-2LKXYpV1H1RkNtE5r5LE6g@mail.gmail.com> (raw)
In-Reply-To: <026301d00ed0$eb723020$c2569060$@alibaba-inc.com>

On 3 December 2014 at 19:12, Hillf Danton <hillf.zj@alibaba-inc.com> wrote:
> Hey Con

Hi Hilf

>> This is to announce a resync and  update of the Brain Fuck Scheduler,
>> version 0.450 for the latest stable linux kernel.
>>
> [...]
>> The patch against linux-3.16(.x) is available here:
>> http://ck.kolivas.org/patches/bfs/3.0/3.16/3.16-sched-bfs-450.patch
>>
> $ grep -nr above_background_load  bfs/src
> bfs/src/3.16-sched-bfs-450.patch:689:+bool above_background_load(void);
> bfs/src/3.16-sched-bfs-450.patch:736:+static inline bool above_background_load(void)
> bfs/src/3.16-sched-bfs-450.patch:1665:+bool above_background_load(void)
>
> Would you please pin-point what is that routine used for?

This function used to be used with the VM tweaks that the -ck patchset
used to come with. I have since deprecated those VM tweaks but the
function remains in the scheduler. You're right to point it out and
I'll remove it when I resync with 3.18 (it's still in the BFS 458
patch for 3.17).

Thanks,
Con

> Thanks
> Hillf
>

  reply	other threads:[~2014-12-07 20:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-03  8:12 [ANNOUNCE] BFS CPU scheduler v0.450 with SMT nice support for linux-3.16 Hillf Danton
2014-12-07 20:26 ` Con Kolivas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-08-16  5:40 Con Kolivas

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=CABqErrEakrJN800zdCMJvmFk0j2-2LKXYpV1H1RkNtE5r5LE6g@mail.gmail.com \
    --to=kernel@kolivas.org \
    --cc=hillf.zj@alibaba-inc.com \
    --cc=linux-kernel@vger.kernel.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 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.