vallor wrote:
$ uname -a Linux lm 6.16.0 #1 SMP PREEMPT Wed Jul 30 18:03:42 PDT 2025stick it up your kernel
x86_64 x86_64 x86_64 GNU/Linux
$ tail -3 linux-6.16/nohup.out real 404.33 user 19235.92 sys 3833.13
$ grep NATIVE linux-6.16/.config CONFIG_CC_HAS_MARCH_NATIVE=y
CONFIG_X86_NATIVE_CPU=y
(Request: Let's keep the topic on Linux, please? :) )
$ uname -a
Linux lm 6.16.0 #1 SMP PREEMPT Wed Jul 30 18:03:42 PDT 2025 x86_64 x86_64 x86_64 GNU/Linux
$ tail -3 linux-6.16/nohup.out
real 404.33
user 19235.92
sys 3833.13
$ grep NATIVE linux-6.16/.config
CONFIG_CC_HAS_MARCH_NATIVE=y
CONFIG_X86_NATIVE_CPU=y
(Request: Let's keep the topic on Linux, please? :) )
Creon wrote:
On Wed, 30 Jul 2025 18:45:43 -0700, % wrote:i know but you didn't have to go tongue first
vallor wrote:
$ uname -a Linux lm 6.16.0 #1 SMP PREEMPT Wed Jul 30 18:03:42 PDT 2025 >>>> x86_64 x86_64 x86_64 GNU/Linuxstick it up your kernel
$ tail -3 linux-6.16/nohup.out real 404.33 user 19235.92 sys 3833.13
$ grep NATIVE linux-6.16/.config CONFIG_CC_HAS_MARCH_NATIVE=y
CONFIG_X86_NATIVE_CPU=y
(Request: Let's keep the topic on Linux, please? :) )
Close.
I've already upped my kernel. So up yours!
Creon wrote:
On Wed, 30 Jul 2025 18:45:43 -0700, % wrote:i know but you didn't have to go tongue first
vallor wrote:
$ uname -a Linux lm 6.16.0 #1 SMP PREEMPT Wed Jul 30 18:03:42 PDTstick it up your kernel
2025 x86_64 x86_64 x86_64 GNU/Linux
$ tail -3 linux-6.16/nohup.out real 404.33 user 19235.92 sys 3833.13
$ grep NATIVE linux-6.16/.config CONFIG_CC_HAS_MARCH_NATIVE=y
CONFIG_X86_NATIVE_CPU=y
(Request: Let's keep the topic on Linux, please? :) )
Close.
I've already upped my kernel. So up yours!
$ uname -a
Linux lm 6.16.0 #1 SMP PREEMPT Wed Jul 30 18:03:42 PDT 2025 x86_64 x86_64 x86_64 GNU/Linux
$ tail -3 linux-6.16/nohup.out
real 404.33
user 19235.92
sys 3833.13
$ grep NATIVE linux-6.16/.config
CONFIG_CC_HAS_MARCH_NATIVE=y
CONFIG_X86_NATIVE_CPU=y
(Request: Let's keep the topic on Linux, please? :) )
On 2025-07-31, vallor <[email protected]> wrote:
$ uname -a
Linux lm 6.16.0 #1 SMP PREEMPT Wed Jul 30 18:03:42 PDT 2025 x86_64 x86_64
x86_64 GNU/Linux
$ tail -3 linux-6.16/nohup.out
real 404.33
user 19235.92
sys 3833.13
$ grep NATIVE linux-6.16/.config
CONFIG_CC_HAS_MARCH_NATIVE=y
CONFIG_X86_NATIVE_CPU=y
(Request: Let's keep the topic on Linux, please? :) )
What distribution are you running?
Also, are you obtaining the source from the official distribution repositories or do you roll your own?
I'm curious because LM which I run, is always way behind the
versions you are upgrading to.
pothead@LinuxMint:~$ uname -a
Linux LinuxMint 6.8.0-64-generic #67-Ubuntu SMP PREEMPT_DYNAMIC Sun Jun 15 20:23:31 UTC 2025 x86_64
x86_64 x86_64 GNU/Linux
On 2025-07-31, vallor <[email protected]> wrote:
$ uname -a Linux lm 6.16.0 #1 SMP PREEMPT Wed Jul 30 18:03:42 PDT 2025
x86_64 x86_64 x86_64 GNU/Linux
$ tail -3 linux-6.16/nohup.out real 404.33 user 19235.92 sys 3833.13
$ grep NATIVE linux-6.16/.config CONFIG_CC_HAS_MARCH_NATIVE=y
CONFIG_X86_NATIVE_CPU=y
(Request: Let's keep the topic on Linux, please? :) )
What distribution are you running?
Also, are you obtaining the source from the official distribution repositories or do you roll your own?
I'm curious because LM which I run, is always way behind the versions
you are upgrading to.
pothead@LinuxMint:~$ uname -a Linux LinuxMint 6.8.0-64-generic
#67-Ubuntu SMP PREEMPT_DYNAMIC Sun Jun 15 20:23:31 UTC 2025 x86_64
x86_64 x86_64 GNU/Linux
What distribution are you running?
Also, are you obtaining the source from the official distribution repositories or do you roll your own?
I'm curious because LM which I run, is always way behind the versions
you are upgrading to.
pothead@LinuxMint:~$ uname -a Linux LinuxMint 6.8.0-64-generic
#67-Ubuntu SMP PREEMPT_DYNAMIC Sun Jun 15 20:23:31 UTC 2025 x86_64
x86_64 x86_64 GNU/Linux
looking for
noticeable differences in performance or behaviour of the machine.
On Thu, 31 Jul 2025 14:28:04 -0000 (UTC), pothead wrote:
On 2025-07-31, vallor <[email protected]> wrote:
$ uname -a Linux lm 6.16.0 #1 SMP PREEMPT Wed Jul 30 18:03:42 PDT 2025
x86_64 x86_64 x86_64 GNU/Linux
$ tail -3 linux-6.16/nohup.out real 404.33 user 19235.92 sys 3833.13
$ grep NATIVE linux-6.16/.config CONFIG_CC_HAS_MARCH_NATIVE=y
CONFIG_X86_NATIVE_CPU=y
(Request: Let's keep the topic on Linux, please? :) )
What distribution are you running?
Linux Mint -- says so in the .sig. :)
Also, are you obtaining the source from the official distribution
repositories or do you roll your own?
I'm curious because LM which I run, is always way behind the versions
you are upgrading to.
I get the latest vanilla kernel from https://kernel.org and NVIDIA drivers from https://nvidia.org -- will have to post instructions when I get a chance. It's not difficult to do, but there is a "gotcha" with Mint:
don't try to use DKMS with NVIDIA drivers, doesn't seem to work right.
pothead@LinuxMint:~$ uname -a Linux LinuxMint 6.8.0-64-generic
#67-Ubuntu SMP PREEMPT_DYNAMIC Sun Jun 15 20:23:31 UTC 2025 x86_64
x86_64 x86_64 GNU/Linux
I've been criticized for taking the time to build and boot the latest
kernel, since the kernel that comes with Linux Mint works just fine.
Eh -- we all have our hobbies.
Creon wrote:
On Thu, 31 Jul 2025 14:28:04 -0000 (UTC), pothead wrote:
On 2025-07-31, vallor <[email protected]> wrote:
$ uname -a Linux lm 6.16.0 #1 SMP PREEMPT Wed Jul 30 18:03:42 PDT
2025 x86_64 x86_64 x86_64 GNU/Linux
$ tail -3 linux-6.16/nohup.out real 404.33 user 19235.92 sys 3833.13
$ grep NATIVE linux-6.16/.config CONFIG_CC_HAS_MARCH_NATIVE=y
CONFIG_X86_NATIVE_CPU=y
(Request: Let's keep the topic on Linux, please? :) )
What distribution are you running?
Linux Mint -- says so in the .sig. :)
Also, are you obtaining the source from the official distribution
repositories or do you roll your own?
I'm curious because LM which I run, is always way behind the versions
you are upgrading to.
I get the latest vanilla kernel from https://kernel.org and NVIDIA
drivers from https://nvidia.org -- will have to post instructions when
I get a chance. It's not difficult to do, but there is a "gotcha" with
Mint: don't try to use DKMS with NVIDIA drivers, doesn't seem to work
right.
pothead@LinuxMint:~$ uname -a Linux LinuxMint 6.8.0-64-generic
#67-Ubuntu SMP PREEMPT_DYNAMIC Sun Jun 15 20:23:31 UTC 2025 x86_64
x86_64 x86_64 GNU/Linux
I've been criticized
and rightly so
Farley Flud <[email protected]> wrote:
My advice:
Stop arguing. Get Gentoo. Optimize. Shut the fuck up.
Totally crazy, mainstream distros are the norm.
Farley Flud <[email protected]> news:pan$ab58a$bf644371$fa8ab850$[email protected] Thu, 31 Jul 2025 18:58:19 GMT in alt.computer.workshop, wrote:
On Thu, 31 Jul 2025 04:46:50 -0000 (UTC), Gremlin wrote:
looking for noticeable differences in performance or behaviour of theWhat do you mean by "noticeable?"
machine.
Human sensory perception cannot detect differences in performance.
Such things must be rigorously measured.
Actually, depending on the hardware; human sensory is fast enough to
catch a performance difference.
In this specific request though, I was asking if they happened to notice
any difference in the systems performance; I assume they also understood
my question was asking how the system 'felt' between the differences.
Does that make better sense?
Farley Flud <[email protected]> news:pan$ab58a$bf644371$fa8ab850$[email protected] Thu, 31 Jul 2025 18:58:19 GMT in alt.computer.workshop, wrote:
On Thu, 31 Jul 2025 04:46:50 -0000 (UTC), Gremlin wrote:
looking for noticeable differences in performance or behaviour of theWhat do you mean by "noticeable?"
machine.
Human sensory perception cannot detect differences in performance. Such
things must be rigorously measured.
Actually, depending on the hardware; human sensory is fast enough to
catch a performance difference.
In this specific request though, I was asking if they happened to notice
any difference in the systems performance; I assume they also understood
my question was asking how the system 'felt' between the differences.
Does that make better sense?
On Sat, 2 Aug 2025 05:30:49 -0000 (UTC), Gremlin wrote:
Again, the CONFIG_X86_NATIVE_CPU option is just a single option that inThe kernel is only an interface to hardware. The system calls
provided by the kernel would not seem to benefit much from a
CONFIG_X86_NATIVE_CPU option:
The intent behind it, (afaik), is to optimize specific routines from
the compilers perspective to better match the hardware it's being ran
on.
and of itself is not likely to lead to a palpable performance boost.
(Example: CONFIG_X86_NATIVE_CPU does not enable Flexible Return and
Event Delivery (FRED) which is a new Intel CPU feature that greatly
improves kernel ring transitions.)
Regrettably, the default kernel happens to be riddled with "security" features that probably degrade performance much more than CONFIG_X86_NATIVE_CPU could override.
For example, the default kernel is built with strong stack protection
which means that a random "canary" is added to subroutines (functions). Calling a function in C is expensive enough but a "canary" only adds
more expense.
Optimizing the kernel to eliminate all that security crud and to select
more performance enhancing features, of which there are also many, is a
BIG job and requires a lot of fundamental understanding of both hardware
and OS design. Fortunately, however, because the kernel is so stable in
its design, if the job is done once it is done practically forever. The
same options can be used over over and over on future kernels.
But there is yet more. The kernel can also be optimized at run time, as opposed to build time. There are many parameters that deal with virtual memory and network throughput that can be tuned by the user. That is
the purpose of the /proc hierarchy as well as the "sysctl" utility.
My advice: Spend some time and effort now to optimize everything and
then you will have a reliable foundation for the future.
The kernel is only an interface to hardware. The system calls provided
by the kernel would not seem to benefit much from a
CONFIG_X86_NATIVE_CPU option:
The intent behind it, (afaik), is to optimize specific routines from the compilers perspective to better match the hardware it's being ran on.
Yes, you read that right: "Farley Flud" wants you to turn off
security mitigations in your kernel. I do not recommend following his advice.
He doesn't run a MAC subsystem either. I strongly recommend
running one to prevent security issues, which Linux Mint does by
default, using AppArmor.
(The alternative in Red Hat / Fedora land is SELinux, which was written
by the NSA.
Might try it with a "native" build of gcc,
On 2 Aug 2025 08:15:32 GMT, vallor wrote:
Might try it with a "native" build of gcc,That wouldn't make any difference.
On 2 Aug 2025 11:14:50 GMT, Creon wrote:
Yes, you read that right: "Farley Flud" wants you to turn off securityYet another human parrot demonstrates his ability to recite the standard dogma without a shred of understanding.
mitigations in your kernel. I do not recommend following his advice.
He doesn't run a MAC subsystem either. I strongly recommend running
one to prevent security issues, which Linux Mint does by default, using
AppArmor.
(The alternative in Red Hat / Fedora land is SELinux, which was writtenThat must explain all those Russian spies that lurk outside my window
by the NSA.
longing to discover my browsing history with a RowHammer attack.
On Sat, 02 Aug 2025 11:59:46 +0000, Farley Flud wrote:
On 2 Aug 2025 11:14:50 GMT, Creon wrote:
Yes, you read that right: "Farley Flud" wants you to turn off securityYet another human parrot demonstrates his ability to recite the standard
mitigations in your kernel. I do not recommend following his advice.
He doesn't run a MAC subsystem either. I strongly recommend running
one to prevent security issues, which Linux Mint does by default, using
AppArmor.
dogma without a shred of understanding.
(The alternative in Red Hat / Fedora land is SELinux, which was writtenThat must explain all those Russian spies that lurk outside my window
by the NSA.
longing to discover my browsing history with a RowHammer attack.
Knowing you, you probably run everything as "root" anyway -- leaving you
one browser exploit away from having your goose thoroughly cooked.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 715 |
| Nodes: | 16 (3 / 13) |
| Uptime: | 29:15:20 |
| Calls: | 12,107 |
| Calls today: | 7 |
| Files: | 15,006 |
| Messages: | 6,518,240 |