BMQ v5.3.1 is released with the following changes
1. Rework sched_rq_watermark. This rework shift the workload of sched_rq_watermaek from ttwu code path to enqueue/dequeue code path. Sanity tests show improvement under all kinds of cpu workload.
2. Fix task_sched_prio(). This fixes a long existed stupid plus/minus one mistake in schedule priority.
Yes, the version number is changed. Now it is better reflect the fact that BMQ is related to the kernel release. In current version pattern, the first two digital is the linux kernel version that this BMQ release is applied on, and 3rd digital is the BMQ release in the given(first 2 digital) kernel.
Enjoy BMQ for your linux kernel, :)
Full kernel tree repository can be found at https://gitlab.com/alfredchen/linux-bmq
And all-in-one patch can be found at gitlab.
Bug report at https://gitlab.com/alfredchen/bmq/issues
Having the two first numbers indicate kernel major is good. 5.3 for 5.3 kernel... easy.
ReplyDeleteUsing the same numbering as the kernel releases could however be somewhat confusing. Does it make it clear that 5.3.1 is for kernel release 5.3.2 or 5.3.12?
What about: 5.3-1 instead? This way it is for 5.3 kernel, and release -1 regardless of what minor version the kernel release is.
Nitpicking perhaps, your choice :)
Good idea, let's begin from next release, ;)
DeleteThis comment has been removed by the author.
ReplyDeleteI suppose that a very optimal solution would be to give the version number 5.X.rY, where:
ReplyDelete- 5.X - kernel line, which seems obvious
- rY - for example r1, r2, r3 - release number, clearly and legibly separated.
Example number:
5.3.r2
There's an error in link to "all-in-one" patch in the blog's notice. The correct is: https://gitlab.com/alfredchen/bmq/blob/master/5.3/bmq_v5.3.1.patch
ReplyDeleteThanks. Updated.
Delete