Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.advocacy > #684368 > unrolled thread

Kerne 6.13 Released

Back to article view | Back to comp.os.linux.advocacy

Contents

  Kerne 6.13 Released Farley Flud <fsquared@fsquared.linux> - 2025-01-20 16:21 +0000
    Linux 6.13 (was: Re: Kerne 6.13 Released) vallor <vallor@cultnix.org> - 2025-01-20 16:47 +0000
      Re: Linux 6.13 CrudeSausage <crude@sausa.ge> - 2025-01-20 11:51 -0500
      Re: Linux 6.13 vallor <vallor@cultnix.org> - 2025-01-20 17:02 +0000
        Re: Linux 6.13 Farley Flud <fsquared@fsquared.linux> - 2025-01-20 17:23 +0000
          Re: Linux 6.13 vallor <vallor@cultnix.org> - 2025-01-20 18:05 +0000
            Re: Linux 6.13 Farley Flud <fsquared@fsquared.linux> - 2025-01-20 18:40 +0000
              Re: Linux 6.13 vallor <vallor@cultnix.org> - 2025-01-20 19:06 +0000
                Re: Linux 6.13 vallor <vallor@cultnix.org> - 2025-01-20 19:26 +0000
                  Re: Linux 6.13 Farley Flud <ff@linux.rocks> - 2025-01-20 20:57 +0000
                    Re: Linux 6.13 vallor <vallor@cultnix.org> - 2025-01-20 21:43 +0000
                      Re: Linux 6.13 Farley Flud <ff@linux.rocks> - 2025-01-20 21:56 +0000
                      Re: Linux 6.13 vallor <vallor@cultnix.org> - 2025-01-21 01:10 +0000

#684368 — Kerne 6.13 Released

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.

Ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha!

But anyway, the poor bastards who are chained to Microslop Winblows
can't even dream of what they are missing.


-- 
Hail Linux!  Hail FOSS!  Hail Stallman!

[toc] | [next] | [standalone]

#684370 — Linux 6.13 (was: Re: Kerne 6.13 Released)

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.)

-- 
-v System76 Thelio Mega v1.1 x86_64 NVIDIA RTX 3090 Ti
   OS: Linux 6.12.10 Release: Mint 21.3 Mem: 258G
   "I do this kind of stuff to him all through the picture."

[toc] | [prev] | [next] | [standalone]

#684371 — Re: Linux 6.13

On 1/20/25 11:47 AM, vallor wrote:
> 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.)

I don't see why I wouldn't use the kernel the distribution hands me, 
especially if it is patched to work properly with the NVIDIA GPUs and 
integrates support for all controllers covered in the xone package.

-- 
CrudeSausage
Gab: @CrudeSausage
Telegram: @CrudeSausage
Unapologetic paleoconservative
KDE supporting member
ASUS Zephyrus GA401QM on Manjaro

[toc] | [prev] | [next] | [standalone]

#684372 — Re: Linux 6.13

On 20 Jan 2025 16:47:03 GMT, vallor <vallor@cultnix.org> wrote in
<lv7d06FhfpoU4@mid.individual.net>:

> 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.)

$ 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

real 382.00
user 17803.06
sys 3573.05

Using NVIDIA-Linux-x86_64-550.142.run still, since the latest release
version of the drivers (NVIDIA-Linux-x86_64-550.144.03.run) complained.

-- 
-v System76 Thelio Mega v1.1 x86_64 NVIDIA RTX 3090 Ti
   OS: Linux 6.13.0 Release: Mint 21.3 Mem: 258G
   ">From my brain, an organ with a mind of its own."

[toc] | [prev] | [next] | [standalone]

#684373 — Re: Linux 6.13

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:27 PST 2025 x86_64 
> x86_64 x86_64 GNU/Linux
> 

Heee, ha, hee, hoo, ha, ha!

You got "PREEMPT_DYNAMIC" which means your distro did the configuring.

But you don't even know what PREEMPT_DYNAMIC means. 


-- 
Hail Linux!  Hail FOSS!  Hail Stallman!

[toc] | [prev] | [next] | [standalone]

#684374 — Re: Linux 6.13

On Mon, 20 Jan 2025 17:23:28 +0000, Farley Flud <fsquared@fsquared.linux>
wrote in <181c7676b8880a9a$115946$445945$802601b3@news.usenetexpress.com>:

> 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:27
>> PST 2025 x86_64 x86_64 x86_64 GNU/Linux
>> 
>> 
> Heee, ha, hee, hoo, ha, ha!
> 
> You got "PREEMPT_DYNAMIC" which means your distro did the configuring.

No, I did that configuring many moons ago.

> But you don't even know what PREEMPT_DYNAMIC means.

Yes I do, and it doesn't mean PREEMPT_LAZY, which is what you said
you were going to configure.  Since you didn't post the output
of uname -a, I suspect you didn't do what you said you were
going to do.

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/kernel/Kconfig.preempt?h=v6.13

config PREEMPT
        bool "Preemptible Kernel (Low-Latency Desktop)"
[...]
          This option reduces the latency of the kernel by making
          all kernel code (that is not executing in a critical section)
          preemptible.  This allows reaction to interactive events by
          permitting a low priority process to be preempted involuntarily
          even if it is in kernel mode executing a system call and would
          otherwise not be about to reach a natural preemption point.
          This allows applications to run more 'smoothly' even when the
          system is under load, at the cost of slightly lower throughput
          and a slight runtime overhead to kernel code.

          Select this if you are building a kernel for a desktop or
          embedded system with latency requirements in the milliseconds
          range.
[...]

And not only that, but you're running the Pan of our forefathers...

-- 
-v System76 Thelio Mega v1.1 x86_64 NVIDIA RTX 3090 Ti
   OS: Linux 6.13.0 Release: Mint 21.3 Mem: 258G
   "Megabyte: A nine course dinner."

[toc] | [prev] | [next] | [standalone]

#684377 — Re: Linux 6.13

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.



-- 
Hail Linux!  Hail FOSS!  Hail Stallman!

[toc] | [prev] | [next] | [standalone]

#684378 — Re: Linux 6.13

On Mon, 20 Jan 2025 18:40:19 +0000, Farley Flud <fsquared@fsquared.linux>
wrote in <181c7aa8579b72e5$175359$891815$802601b3@news.usenetexpress.com>:

> 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?)

-- 
-v System76 Thelio Mega v1.1 x86_64 NVIDIA RTX 3090 Ti
   OS: Linux 6.13.0 Release: Mint 21.3 Mem: 258G
   "Please Tell Me if you Don't Get This Message"

[toc] | [prev] | [next] | [standalone]

#684379 — Re: Linux 6.13

On 20 Jan 2025 19:06:42 GMT, vallor <vallor@cultnix.org> wrote in
<lv7l61Fkht9U1@mid.individual.net>:

> Eh, I'll give you that one, because I had it checked.  Standby on that.

$ uname -a
Linux lm 6.13.0 #1 SMP PREEMPT Mon Jan 20 10:58:30 PST 2025 x86_64 x86_64 
x86_64 GNU/Linux

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.

Do...do you need help?

> 
> 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?)

-- 
-v System76 Thelio Mega v1.1 x86_64 NVIDIA RTX 3090 Ti
   OS: Linux 6.13.0 Release: Mint 21.3 Mem: 258G
   "90% of being smart is knowing what you're dumb at."

[toc] | [prev] | [next] | [standalone]

#684385 — Re: Linux 6.13

On 20 Jan 2025 19:26:12 GMT, vallor wrote:

> 
> 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.
>

What's the rush, idiot?

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. 


-- 
Systemd: solving all the problems that you never knew you had.

[toc] | [prev] | [next] | [standalone]

#684394 — Re: Linux 6.13

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".
>> 
>> Wotta wuss!  I'll bet you couldn't get 6.13 to build the way you wanted
>> it to.
>>
>>
> What's the rush, idiot?
> 
> 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?

-- 
-v System76 Thelio Mega v1.1 x86_64 NVIDIA RTX 3090 Ti
   OS: Linux 6.13.0 Release: Mint 21.3 Mem: 258G
   "Artificial Intelligence is no match for natural stupidity."

[toc] | [prev] | [next] | [standalone]

#684396 — Re: Linux 6.13

On 20 Jan 2025 21:43:41 GMT, vallor wrote:

> 
> Do...do you need help?
>

The whole group needs help in keeping you idiots out of here
so that we can have meaningful and productive discussions about
the superiority of GNU/Linux.





-- 
Systemd: solving all the problems that you never knew you had.

[toc] | [prev] | [next] | [standalone]

#684398 — Re: Linux 6.13

On 20 Jan 2025 21:43:41 GMT, vallor <vallor@cultnix.org> wrote in
<lv7ucdFm488U1@mid.individual.net>:

> 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".
>>> 
>>> Wotta wuss!  I'll bet you couldn't get 6.13 to build the way you
>>> wanted it to.
>>>
>>>
>> What's the rush, idiot?
>> 
>> 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?

(Short answer:  He needs help!)

What is it about this new Linux kernel that has you confounded?

-- 
-v System76 Thelio Mega v1.1 x86_64 NVIDIA RTX 3090 Ti
   OS: Linux 6.13.0 Release: Mint 21.3 Mem: 258G
   "Printed on 100% recyclable phosphor."

[toc] | [prev] | [standalone]

Back to top | Article view | comp.os.linux.advocacy

csiph-web