Sender: Tejun Heo <htejun@gmail.com>
Date:   Mon, 30 Jan 2023 14:36:25 -1000
From:   Tejun Heo <tj@kernel.org>
To:     Josh Don <joshdon@google.com>
Cc:     torvalds@linux-foundation.org, mingo@redhat.com,
        peterz@infradead.org, juri.lelli@redhat.com,
        vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
        rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
        bristot@redhat.com, vschneid@redhat.com, ast@kernel.org,
        daniel@iogearbox.net, andrii@kernel.org, martin.lau@kernel.org,
        brho@google.com, pjt@google.com, derkling@google.com,
        haoluo@google.com, dvernet@meta.com, dschatzberg@meta.com,
        dskarlat@cs.cmu.edu, riel@surriel.com,
        linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
        kernel-team@meta.com
Subject: Re: [PATCH 27/30] sched_ext: Implement core-sched support
Message-ID: <Y9hiifiFx4TeUdTo@slm.duckdns.org>
References: <20230128001639.3510083-1-tj@kernel.org>
 <20230128001639.3510083-28-tj@kernel.org>
 <CABk29Nt2-CCGnogpfEgJ3ZDk5Esk04n6EwsAqpw_vdeVfKuFUQ@mail.gmail.com>
 <Y9hgLENFI5y3Qtx2@slm.duckdns.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Y9hgLENFI5y3Qtx2@slm.duckdns.org>
Precedence: bulk

On Mon, Jan 30, 2023 at 02:26:20PM -1000, Tejun Heo wrote:
> However, the BPF scheduler is free to dispatch whatever tasks anytime (e.g.
> scx_example_central), so it's possible that a task with an earlier timestamp
> has been dispatched to the local DSQ since curr started executing, in which
> case we likely want to return the first on DSQ as the CPU's candidate.

Okay, a more common case would be when a CPU is forced to run a task which
isn't current by its sibling winning a different cookie and then the BPF
scheduler putting that task right back on the local DSQ. For the CPU then,
the right candidate would be the first task on DSQ not the current running
one which is dragged forward because the sibling trumping us.

Thanks.

-- 
tejun