linux-kernel - BF Kernel ? (was Low JItter, Fair Pay Philosophy, BF Unification)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <f566804f-2c11-4ef8-8fa9-1a9ec3584917@bit-el.eu>
Date: Fri, 19 Sep 2025 11:13:48 +0200
From: Ywe Cærlyn <Budi@...-el.eu>
To: linux-kernel@...r.kernel.org
Subject: BF Kernel ? (was Low JItter, Fair Pay Philosophy, BF Unification)

Seeing corrodation symbols in the kernel (germ, rust, breakpoints 
outside scheduler etc) I suggest:

BF Kernel.

  - lightweight kernel threads standard
  - breaking/context switch ofcourse inside scheduler/inner loop, using 
cache properly (256kb cache target, well done programming needs no more)
  - no 10ms filter in sched.c, most things have happened by then. 
Instant available resources ofcourse.
  - no heuristics. One needs to set priorities etc. oneself.

Using Lambda subset of C, for later Lambda CPU.

Light,
Ywe.
https://bit-el.eu/