From: Farley Flud <ff@linux.rocks>
Subject: Re: All Done!  Xeon W-1270P is Now Officially Complete
Newsgroups: comp.os.linux.advocacy
References: <pan$c8bc$a915b81c$c41413ac$4e3b8572@linux.rocks> <67c2db10$0$433$426a74cc@news.free.fr>
Mime-Version: 1.0
Message-Id: <pan$41049$5e3ed40b$5dd8c9d7$15652c37@linux.rocks>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Lines: 36
Path: ...!weretis.net!feeder9.news.weretis.net!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!feeder.usenetexpress.com!tr2.iad1.usenetexpress.com!news.usenetexpress.com!not-for-mail
Date: Sat, 01 Mar 2025 12:14:54 +0000
Nntp-Posting-Date: Sat, 01 Mar 2025 12:14:54 +0000
X-Received-Bytes: 1609
Organization: UsenetExpress - www.usenetexpress.com
X-Complaints-To: abuse@usenetexpress.com
Bytes: 1928

On 01 Mar 2025 10:01:52 GMT, Stéphane CARPENTIER wrote:

> 
>> Cache optimization is extremely critical.
> 
> Yes. And difficult. With each one of your messages, you proved you
> aren't able to manage it. You should let your distro take care of it.
> You will only result with a messed up computer.
>

Ha, ha, ha, ha, ha!  Totally wrong!

The gcc compiler can optimize programs only if if knows
the cache size in advance.  GCC can be informed of the exact
cache size by using the following options:

--param l1-cache-size=X
--param l1-cache-line-size=Y
--param l2-cache-size=Z

These options are automatically passed to GCC when using
the "-march-native" option.

Distros cannot do this.  Distros most likely use
the options "-mtune=generic -march=x86-64" which does
not pass any information about cache size to GCC (how
could it?).

Consequently, the programs distributed with a distro
are NOT optimized to use the CPU cache.

Consequently, you are an IDIOT.


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