[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALOAHbC0xNnqWt=og+g=DT0yRqST6cTAUvZkQ-7o8Nw8O-2J9w@mail.gmail.com>
Date: Thu, 25 Nov 2021 14:00:04 +0800
From: Yafang Shao <laoar.shao@...il.com>
To: Roman Gushchin <guro@...com>
Cc: Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
Mel Gorman <mgorman@...hsingularity.net>,
bpf <bpf@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH rfc 0/6] Scheduler BPF
Hi Roman,
Scheduler BPF is a great idea.
Thanks for the work.
Scheduler BPF won’t be a small feature, I think we’d better give a
summary of possible hooks it may add first.
We must have a *basic rule* to control what it will tend to be to
avoid adding BPF hooks here and there.
I haven’t found a clear rule yet, but maybe we can learn it from
netfilter, which has 5 basic hooks.
Regarding the scheduler BPF hooks, some possible basic hooks may be:
- Hook for Enqueue
- Hook for Dequeue
- Hook for Put Prev Task
- Hook for Set Next Task
> An example of an userspace part, which loads some simple hooks is available
> here [3]. It's very simple, provided only to simplify playing with the provided
> kernel patches.
>
You’d better add this userspace code into samples/bpf/.
[Some error occurs in my mail client, so I resend it]
--
Thanks
Yafang
Powered by blists - more mailing lists