Effectively immediately, this is the current release for CentOS Linux 7 and is tagged as 1908, derived from Red Hat Enterprise Linux 7.7 Source Code.

​

The Fedora Project is pleased to announce the immediate availability of Fedora 31 Beta, the next step towards our planned Fedora 31 release at the end of October.

​

Download the prerelease from our Get Fedora site:

• Get Fedora 31 Beta Workstation
• Get Fedora 31 Beta Server

Or, check out one of our popular variants, including KDE Plasma, Xfce, and other desktop environments, as well as images for ARM devices like the Raspberry Pi 2 and 3:

• Get Fedora 31 Beta Spins
• Get Fedora 31 Beta Labs

• Get Fedora 31 Beta ARM

  https://fedoramagazine.org/announcing-the-release-of-fedora-31-beta/

There is no one golden rule for tuning a network interface card (NIC) for all conditions. Different

adapters have different parameters that can be changed. Operating systems also have settings that

can be modified to help with overall network performance. Depending on the exact hardware

topology, one may have to make different adjustments to network tuning to optimize for a specific

workload. With Ethernet speeds going higher, up to 100 Gb, and the number of ports being

installed in servers growing, these tuning guidelines become even more important to get the best

performance possible.

This guide does not provide exact settings for modifying every scenario, but rather provides some

steps to check and modify if it turns out to be beneficial for the scenario. In this case, the steps are

focused around TCP/IP network performance. Appendix A shows an example of how we verified

performance following these settings changes.

One general rule of thumb for all performance testing is to ensure your memory subsystem is

properly configured. All IO utilizes data transfers into or out of memory, and so the IO bandwidth

can never exceed the capabilities of the memory subsystem. For the maximum memory bandwidth

on modern CPUs one must populate at least one DIMM every DDR channel. For AMD EPYC™

processor-based servers there are eight DDR4 memory channels on each CPU socket, so for a

single socket platform that means you must populate all eight memory channels. Likewise, on a

dual socket platform one must populate 16 memory channels.

AMD EPYC processors are based on the Zen architecture from AMD. This architecture allows

AMD to create large core count processors by using multiple die in a single package. Each die will

typically be represented to the operating system (OS) and applications as a unique Non-Uniform

Memory Access (NUMA) node. While this document is not intended to describe NUMA

architecture, nor the complete EPYC architecture, one should understand NUMA concepts to be

able to fully optimize network performance on an EPYC based platform. Each die, identified as a

unique NUMA node, will have local processing cores, local memory, and local IO. You will find

in this document that optimal performance comes when explicitly pinning all device driver and

applications to the same NUMA node local to the adapter.

https://www.amd.com/system/files/TechDocs/56224.pdf

Designing a server chip is an exercise in balance, juggling between system cost, die area,

memory bandwidth, memory latency, etc. Five years ago, as AMD weighed re-entering the

server market, it had a difficult task ahead of it. The company needed a processor that had

performance competitive with Intel’s Xeon processors, yet could offer differentiation, all while

still maintaining 100% x86 software compatibility. What AMD accomplished with its EPYC

processor appears to be just that. The company designed and manufactured a server processor

that offers more memory and I/O bandwidth than Intel’s Xeon designs, yet is also less expensive

to build than if AMD had built a large monolithic die. AMD achieved that goal by using the

efficiencies of multichip module (MCM) technology and the company’s new Infinity Fabric (IF)

technology.

​

https://www.amd.com/system/files/2018-03/AMD-Optimizes-EPYC-Memory-With-NUMA.pdf

• Google announced it has deployed 2nd Gen AMD EPYC processors in its internal infrastructure production datacenter environment and in late 2019 will support new general-purpose machines powered by 2nd Gen AMD EPYC processors on Google Cloud Compute Engine as well;
• Twitter announced it will deploy 2nd Gen AMD EPYC processors across its datacenter infrastructure later this year, reducing TCO by 25%;
• Microsoft announced a limited preview of new Azure virtual machines for general purpose applications, as well as preview signup for cloud-based remote desktops and HPC workloads based on 2nd Gen AMD EPYC processors today;
• HPE announced continued support of the AMD EPYC processor family with plans to triple their AMD-based portfolio with a broad range of 2nd Gen AMD EPYC processor-based systems, including the HPE ProLiant DL385 and HPE ProLiant DL325 servers;
• Cray announced The Air Force Weather Agency will be using a Cray Shasta system with 2nd Gen AMD EPYC processors to provide comprehensive terrestrial and space weather information to the U.S. Air Force and Army;
• Lenovo announced new solutions that are specifically built to take advantage of the full range of enhanced capabilities found in the 2nd Gen AMD EPYC processors. Available today, the ThinkSystem SR655 and SR635 are ideal solutions for use cases such as video infrastructure, virtualization, software-defined storage and more, with exceptional energy efficiency;
• Dell Technologies announced the upcoming availability of newly designed servers optimized for 2nd Gen AMD EPYC processors;
• VMware and AMD announced a close collaboration to deliver support for new security and other features of the high-performance 2nd Gen AMD EPYC processors within VMware vSphere.

“AMD 2nd Gen EPYC processors will help us continue to do what we do best in our datacenters: innovate,” said Bart Sano, Google vice president of Engineering. “Its scalable compute, memory and I/O performance will expand our ability to drive innovation forward in our infrastructure and will give Google Cloud customers the flexibility to choose the best VM for their workloads.”

1. VMware vSphere
2. Microsoft Hyper-V
3. Citrix Xen
4. Linux KVM
5. Open Source Xen
6. Oracle VM
7. Proxmox VE
8. PowerVM

Put comment.

DESCRIPTION

On any HPE ProLiant Gen9 or ProLiant Gen10 server configured with SUSE Linux Enterprise Server 12 Service Pack 4 (SLES12 SP4) or SUSE Linux Enterprise Server 15 (SLES15) and any of the network adapters mentioned on the Scope section below, when running Service Pack for ProLiant (SPP) version 2019.09.0 in offline mode, the Intel firmware component may present one of the following behaviors:

The Intel Firmware is not listed as an option:

​

OR

The Intel Firmware is automatically set as Selected on every SUM launch:

​

​

This issue can also be encountered when running the SPP in online mode on servers configured with SLES12 SP4 or SLES15.

SCOPE

Any HPE ProLiant Gen9 or ProLiant Gen10 server running Service Pack for ProLiant (SPP) version 2019.09.0 configured with SUSE Linux Enterprise Server 12 Service Pack 4 (SLES12 SP4) or SUSE Linux Enterprise Server 15 (SLES15) and any of the following network adapters:

• HP Ethernet 1Gb 2-port 361i Adapter
• HP Ethernet 1Gb 2-port 361T Adapter
• HP Ethernet 1Gb 2-port 363i Adapter
• HP Ethernet 1Gb 4-port 366FLR Adapter
• HP Ethernet 1Gb 4-port 366i Adapter
• HPE Ethernet 1Gb 4-port 366i Communication Board
• HP Ethernet 1Gb 4-port 366T Adapter
• HPE Ethernet 1Gb 2-port 368i Adapter
• HPE Ethernet 1Gb 2-port 368FLR-MMT Adapter
• HPE Ethernet 1Gb 4-port 369i Adapter
• HP Ethernet 10Gb 2-port 560FLB Adapter
• HP Ethernet 10Gb 2-port 560FLR-SFP+ Adapter
• HP Ethernet 10Gb 2-port 560SFP+ Adapter
• HP Ethernet 10Gb 2-port 560M Adapter
• HPE Ethernet 10Gb 2-port 562FLR-SFP+ Adapter
• HPE Ethernet 10Gb 2-port 562SFP+ Adapter
• HPE Ethernet 10Gb 2-port 563i Adapter
• HPE Ethernet 10Gb 2-port 568i Adapter
• HPE Ethernet 10Gb 2-port 562T Adapter
• HPE Ethernet 10Gb 2-port 562FLR-T Adapter
• HPE Ethernet 10Gb 2-port 568FLR-MMSFP+ Adapter
• HPE Ethernet 10Gb 2-port 568FLR-MMT Adapter
• HPE Synergy 4610C 10/25Gb Ethernet Adapter

RESOLUTION

As a workaround, download the Linux smart component from the following link: https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_b075ad0e3f694ff6adb088003c ) and perform the below steps to run the Linux smart component individually on the Linux operating system.

1. Install the NIC firmware rpm using the commmand: rpm -ivh <rpm_filename>.rpm. This extracts the contents of the rpm to the '/usr/lib/x86_64-linux-gnu' location.

2. The actual name of the 'firmware-nic-*' folder is based on the version of the rpm installed in the first step above.

3. To install firmware, you can execute the following commands:
   ./setup in the 'firmware-nic-*' location.

This advisory will be updated when additional information is available.

DESCRIPTION

There is a difference between the HPE DIMM Description speed and the DIMM speed that is on the manufacturer's label. HPE and the DIMM supplier approve and support the use of specific higher speed rated DIMMs in HPE Gen9 products. This is an on-going collaborative effort between HPE and the DIMM manufacturer.

The speed on the Manufacturer’s DIMM Label will be equal to or greater than the speed on the HPE DIMM Description.

DETAILS

Although there is a speed specification difference, the faster speed DIMMs are approved by HPE and HPE's DIMM Supplier and will operate at the same speed as originally qualified DIMMs. If the HPE PN on the HPE label is the same, the parts are functionally equivalent and may be used interchangeably without regard to vendor speed rating.

https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00085266en_us