Kernel 6.13 is released.
The big thing is "Lazy Premption."
I'm gonna build my 6.13 with lazy premption.
I wonder what the distros will do? But whatever it is the
distro lackeys will be sure to follow.
On Mon, 20 Jan 2025 16:21:25 +0000, Farley Flud <fsquared@fsquared.linux> wrote in <181c7313cfa9597f$23835$1825$802601b3@news.usenetexpress.com>:
Kernel 6.13 is released.
The big thing is "Lazy Premption."
I'm gonna build my 6.13 with lazy premption.
I wonder what the distros will do? But whatever it is the
distro lackeys will be sure to follow.
Except, you're a distro lacky youself -- running an old Pan,
as well as running the kernel your distro hands you.
Have you ever done anything on your own? Let's see some
of your "perfect" C code.
(Hell, you haven't posted your subfactorial code yet...but
I have. Tsk, tsk.)
On Mon, 20 Jan 2025 16:21:25 +0000, Farley Flud<fsquared@fsquared.linux>
wrote in <181c7313cfa9597f$23835$1825$802601b3@news.usenetexpress.com>:
Kernel 6.13 is released.
The big thing is "Lazy Premption."
I'm gonna build my 6.13 with lazy premption.
I wonder what the distros will do? But whatever it is the
distro lackeys will be sure to follow.
Except, you're a distro lacky youself -- running an old Pan,
as well as running the kernel your distro hands you.
Have you ever done anything on your own? Let's see some
of your "perfect" C code.
(Hell, you haven't posted your subfactorial code yet...but
I have. Tsk, tsk.)
On Mon, 20 Jan 2025 17:02:47 +0000, vallor wrote:
$ uname -a Linux lm 6.13.0 #1 SMP PREEMPT_DYNAMIC Mon Jan 20 08:35:27Heee, ha, hee, hoo, ha, ha!
PST 2025 x86_64 x86_64 x86_64 GNU/Linux
You got "PREEMPT_DYNAMIC" which means your distro did the configuring.
But you don't even know what PREEMPT_DYNAMIC means.
$ uname -a
Linux lm 6.13.0 #1 SMP PREEMPT_DYNAMIC Mon Jan 20 08:35:27 PST 2025 x86_64 x86_64 x86_64 GNU/Linux
PREEMPT_DYNAMIC
On Mon, 20 Jan 2025 18:05:29 +0000, vallor wrote:
PREEMPT_DYNAMIC
You copied the wrong section:
config PREEMPT_DYNAMIC
bool "Preemption behaviour defined on boot"
depends on HAVE_PREEMPT_DYNAMIC
select JUMP_LABEL if HAVE_PREEMPT_DYNAMIC_KEY
select PREEMPT_BUILD
default y if HAVE_PREEMPT_DYNAMIC_CALL
help
This option allows to define the preemption model on the kernel
command line parameter and thus override the default preemption
model defined during compile time.
***----> The feature is primarily interesting for Linux distributions which
provide a pre-built kernel binary to reduce the number of kernel
flavors they offer while still offering different usecases.
The runtime overhead is negligible with HAVE_STATIC_CALL_INLINE enabled
but if runtime patching is not available for the specific architecture
then the potential overhead should be considered.
Interesting if you want the same pre-built kernel should be used for
both Server and Desktop workloads.
Eh, I'll give you that one, because I had it checked. Standby on that.
Meanwhile, you *still* haven't posted your uname -a, and you *still*
haven't built the latest Pan, and you *still* haven't posted
your "perfect" C code that uses gmp to compute subfactorials.
(BTW, have you figured out yet why you don't want PREEMPT_LAZY?)
Meanwhile, we *still* haven't seen your "uname -a".
Wotta wuss! I'll bet you couldn't get 6.13 to build the way
you wanted it to.
On 20 Jan 2025 19:26:12 GMT, vallor wrote:
Meanwhile, we *still* haven't seen your "uname -a".What's the rush, idiot?
Wotta wuss! I'll bet you couldn't get 6.13 to build the way you wanted
it to.
I'm waiting for the new release of the GNU C Library, which should be in
the first week of February (they release twice a year, in August and February).
Then, I can build 6.13 and glibc and gcc. This is necessary because of
GCC's "fixincludes" step.
But you wouldn't know anything about fixincludes.
Idiot.
copping out<<<
Do...do you need help?
On Mon, 20 Jan 2025 20:57:19 +0000, Farley Flud <ff@linux.rocks> wrote
in <pan$14494$d5bd14d6$a2ad0637$92a40b84@linux.rocks>:
On 20 Jan 2025 19:26:12 GMT, vallor wrote:
Meanwhile, we *still* haven't seen your "uname -a".What's the rush, idiot?
Wotta wuss! I'll bet you couldn't get 6.13 to build the way you
wanted it to.
I'm waiting for the new release of the GNU C Library, which should be
in the first week of February (they release twice a year, in August and
February).
Then, I can build 6.13 and glibc and gcc. This is necessary because of
GCC's "fixincludes" step.
But you wouldn't know anything about fixincludes.
Idiot.
Cool sig, Bro, but looks like to me that you're
copping out<<<
Wuss. So I'll just assume you couldn't build the kernel you said you
wanted to.
Do...do you need help?
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 546 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 162:01:30 |
| Calls: | 10,385 |
| Calls today: | 2 |
| Files: | 14,057 |
| Messages: | 6,416,500 |