Leaderboard

Hello Everyone -- I want to highlight some improvements that have been made to the wiki besides our new FAQ (https://www.funtoo.org/FAQ) We now have a new Subarches page that is a lot easier to navigate: https://www.funtoo.org/Subarches And the look of various things like notes, tips, warnings, etc. have been improved for a cleaner, more consistent look. This is a good sample page to browse the new look. Note that you may need to "hard reload" the page to get the new CSS: https://www.funtoo.org/Upgrade_Instructions Enjoy! -Daniel

Recently I fell into the trap having march=skylake in my CFLAGS which is not really supported by GCC 7. Now I have fixed this by setting CFLAGS march option to broadwell which makes sense and works so far. Thanks to all the people involved doing the hard work on that beast! To squeeze out the last bit of my CPU I wonder if it makes sense to adjust the CPU_FLAGS_X86 setting to the output I am getting from the cpuid2cpuflags tool. The output I am getting does differ from the recommendation on the subarches wiki page for skylake and the given x86-64bit make.defaults for Intel Skylake. Could the output be different because I have a Xeon E3 instead of an iCore 3/5/7? My ego profile shows the following: arch: x86-64bit build: current subarch: intel64-skylake The basic CPU_FLAGS_X86 option for Intel Skylake is according to the Subarches page: aes avx avx2 fma3 mmx mmxext popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3 make.defaults for x86-64-bit Intel skylake contains the following (difference underlined): aes avx avx2 f16c fma3 mmx mmxext popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3 cpuid2cpuflags for my Xeon E3 v5 states there is another option available (difference underlined): aes avx avx2 f16c fma3 mmx mmxext pclmul popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3 It seems like f16c and pclmul are not used in many packages explicitly. But I am also compiling non-ebuild stuff and some stuff from my own overlay. In general I have not that much insight how CPU flags are used and I do not know if the compilation of GCC with those additional flags would automagically improve compilation results in general. So my question is: would it be of any benefit to modify the CPU_FLAGS_X86 flag to reflect what cpuid2cpuflags spits out? Thanks! eyesee

Hi All, As we move to our third-generation infrastructure, I am currently migrating containers to BTRFS+SSD (from ZFS and HDD+Optane) which may result in up to an hour of downtime, especially if you have a lot of data stored in your containers. But the result will be much, much, much faster IO. So if you have seen your uptime on your container change recently, this is why. Best, Daniel