From: Con Kolivas <con@kolivas.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] linux-7.2-ck1, MuQSS CPU scheduler for linux-7.2
Date: Tue, 18 Aug 2026 06:34:01 +1000 [thread overview]
Message-ID: <CABqErrEr-RtLSZzF1O5+vwf7ZTn_ScRpar1k11exvAkLdhkcBQ@mail.gmail.com> (raw)
In-Reply-To: <87zeykbyw2.fsf@trenco.lwn.net>
On Tue, 18 Aug 2026 at 00:33, Jonathan Corbet <corbet@lwn.net> wrote:
>
> Con Kolivas <con@kolivas.org> writes:
>
> > Announcing the return of the first stable version of my out-of-tree
> > patchset - not for mainline inclusion consideration.
> >
> > Tag:
> > https://github.com/ckolivas/linux/releases/tag/v7.2-ck1
> > Tree:
> > https://github.com/ckolivas/linux/tree/7.2-ck
> >
> > The -ck patchset aims to improve desktop/mobile device responsiveness,
> > interactivity, and gaming, mostly by replacing the CPU scheduler
> > en-bloc with my EEVDF, configurable runqueue sharing, MultiQueue
> > Skiplist Scheduler.
> >
> > It's been 10 years since I originally abandoned the patchset for time
> > reasons, but LLMs have made merging and development infinitely easier.
>
> I'm genuinely curious: have you considered moving this work to
> sched_ext? That would instantly make it much more widely available for
> people to try out and actually use.
Considered yes. It would work for the scheduling policy but there's no
way to extend it to runqueue sharing which provides half the benefit.
Thanks,
Con
>
> Thanks,
>
> jon
next prev parent reply other threads:[~2026-08-17 20:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 2:32 Con Kolivas
2026-08-17 14:33 ` Jonathan Corbet
2026-08-17 20:34 ` Con Kolivas [this message]
2026-08-22 14:21 ` Steven Rostedt
2026-08-22 22:25 ` Con Kolivas
2026-08-23 2:08 ` Con Kolivas
2026-08-23 14:28 ` Steven Rostedt
2026-08-23 14:54 ` 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=CABqErrEr-RtLSZzF1O5+vwf7ZTn_ScRpar1k11exvAkLdhkcBQ@mail.gmail.com \
--to=con@kolivas.org \
--cc=corbet@lwn.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®