Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Is rebasing the sched_ext tree on top of upstream kernel the best method for testing against an upstream baseline? I thought I'd start testing by running a performance comparison between the current release kernel (6.3) and sched_ext with no special scheduling active to verify my assumption that there will be no perf delta without a special scheduler active. I rebased https://github.com/sched-ext/sched_ext/commit/82f404e53de0ac00040bccf2f7719159c25d4a11 on https://github.com/torvalds/linux/commit/457391b0380335d5e9a5babdec90ac53928b23b4 with no significant conflicts (just one documentation conflict), but I'm encountering the following error during build, which makes me uncertain that the rebase was clean:
Is rebasing the sched_ext tree on top of upstream kernel the best method for testing against an upstream baseline? I thought I'd start testing by running a performance comparison between the current release kernel (6.3) and sched_ext with no special scheduling active to verify my assumption that there will be no perf delta without a special scheduler active. I rebased https://github.com/sched-ext/sched_ext/commit/82f404e53de0ac00040bccf2f7719159c25d4a11 on https://github.com/torvalds/linux/commit/457391b0380335d5e9a5babdec90ac53928b23b4 with no significant conflicts (just one documentation conflict), but I'm encountering the following error during build, which makes me uncertain that the rebase was clean: