当前位置：文档之家 › CoreSPI_HB

CoreSPI_HB

  • 格式：doc
  • 大小：1.07 MB
  • 文档页数：17

CoreSPI v3.0手册一、内核概述串行外设接口（SPI）总线允许微处理器/微控制器和外围设备之间高速的同步串行数据传输。

CoreSPI能实现串行外设接口，同时也能作为主机或从机进行操作。

在主模式下运行时，核产生串行数据时钟（m_sck），并选择从器件进行访问。

在从动模式下运行时，另一个主器件产生s_sck时钟并且激活从机，选择数据输入核心连接运行。

SPI从机进行了精心设计从而使提供最可靠的通信成为可能。

要实现一个时钟域的设计，必须对s_sck线进行采样并与系统时钟同步。

这额外的好处是能增加s_sck线路噪声和毛刺的宽度。

设计是完全同步的，并有一个系统时钟的时钟域。

这将更可靠，无故障合成和实施的核心。

没有使用特殊的技术功能，所以源HDL代码可以很容易地转移到任何技术。

在核中合成的其他功能还包括支持在主模式运行时，有8个从机线用于访问多达8个设备，并且能选择位的传输顺序（MSB在前或者LSB在前），从而节省工作时宝贵的时间不执行此功能的软件。

图1：CoreSPI框图二、关键的功能1、全双工，同步，8位传输串行数据2、高比特率3、主模式或者从模式4、在主模式下产生的比特率：1/2，1/4，1/8，1/16，1/32，1/64，1/128，1/256对f PCLK5、在从模式下支持的比特率:f PCLK f PCLK/26、8从机选择线7、MSB优先或者LSB优先进行数据传递8、一个时钟域的完全同步设计三、支持的器件系列1、Fusion(融合)2、IGLOO™3、IGLOOe4、ProASIC®3L5、ProASIC36、ProASIC3E四、设备利用率和性能CoreSPI可以在任何Actel的设备上实现。

CoreSPI各种设备的利用率和性能的总结在表1到表3中列出。

用于布局的速度等级如下：IGLOO系列：STD，融合：-2，ProASIC3 / E：-2，ProASIC PLUS®：STD，Axcelerator®：-2，RTAX - S：-1。

表1：CoreSPI设备利用率和性能（组合模式）器件系列瓦利用率性能顺序组合总的设备总的Fusion 109 221 330 AFS600-2 2.4% 131MHZ IGLOO 109 218 327 AGL600-STD 2.4% 80MHZ ProASIC3/E 109 221 330 M7A3P250-2 5.4% 134MHZ ProASIC PLUS109 300 409 APA075-STD 13.3% 85MHZ Axcelerator 107 152 259 AX250-2 6.1% 190MHZ RTAX-S 107 152 259 RTAX250S-1 6.1% 136MHZ 注：表1中的数据使用典型的合成和布局设置。

顶级参数/泛型设置如下：MASTER_MODE= 1，SLAVE_MODE= 1。

表2：CoreSPI设备利用率和性能（仅限主模式）器件系列瓦利用率性能顺序组合总的设备总的Fusion 81 182 263 AFS600-2 1.9% 131MHZ IGLOO 81 181 262 AGL600-STD 1.9% 86MHZ ProASIC3/E 81 182 263 M7A3P250-2 4.3% 126MHZ ProASIC PLUS78 237 315 APA075-STD 10.3% 87MHZ Axcelerator 79 127 206 AX250-2 4.9% 188MHZ RTAX-S 79 127 206 RTAX250S-1 4.9% 138MHZ 注：表2中的数据使用典型的合成和布局设置。

顶级参数/泛型设置如下：MASTER_MODE=1，SLAVE_MODE= 0。

表3： CoreSPI设备利用率和性能（仅限从模式）器件系列瓦利用率性能顺序组合总的设备总的Fusion 94 100 194 AFS600-2 1.4% 196MHZ IGLOO 94 102 196 AGL600-STD 1.4% 107MHZ ProASIC3/E 94 100 194 M7A3P250-2 3.2% 202MHZ ProASIC PLUS50 134 184 APA075-STD 6.0% 144MHZ Axcelerator 50 66 116 AX250-2 2.8% 292MHZ RTAX-S 60 66 116 RTAX250S-1 2.8% 207MHZ 注：表3中的数据使用典型的合成和布局设置。

顶级参数/泛型设置如下：MASTER_MODE= 0，SLAVE_MODE= 1。

（一）功能块描述CoreSPI主要是一个状态机，用于连接串行外设接口到高级外设总线（APB）接口。

图1显示了CoreSPI框图。

以下将描述了每个块的功能。

一、APB接口CoreSPI支持APB接口兼容Actel的Cortex™- M1的Core8051s，CoreMP7的处理器内核和CoreABC通用状态机的控制核心（简单的FSM的应用）。

这个接口提供了直接访问核心的内部寄存器（见第七页表6：CoreSPI内部寄存器注册指南）。

二、μController接口μController接口块是用来翻译APB读写命令并对SFR（特殊功能寄存器）进行读取和写入，以及提供SPI主模式和SPI从模式的控制逻辑。

三、SPI主模式SPI主模块是用来跟踪和更新，显示CoreSPI主模式功能状态的状态机。

它包含一个SPI接口去控制从模式，接口包括一条时钟线（SCK）和一条数据线（SS）。

四、SPI从模式SPI主模块是用来跟踪和更新，显示CoreSPI从模式功能状态的状态机。

它包含一个SPI接口给主模式控制，接口包括一条时钟线（SCK）和一条数据线（SS）。

(二)工具流程一、许可证CoreSPI在三个方面被授权。

根据您的许可证，工具流功能可能会受到限制。

二、评价提供预编译的仿真库，允许核心在CoreConsole被实例化并且在Actel公司的Libero®集成设计环境（IDE）中进行模拟。

设计不能合成的，同时也不提供源代码。

三、模糊处理（Obfuscated）为核心提供完整的RTL代码，允许核心在CoreConsole中实例化，在Libero IDE中仿真，综合，布局。

为核心的RTL代码是模糊处理的。

四、RTL为核心和测试平台提供完整的RTL源代码。

五、核心控制台（CoreConsole）CoreSPI是预装在CoreConsole IP开发平台（IDP）。

要使用核心时，只需将它从IP核心列表拖动到主窗口。

然后核心可以配置使用范围内的CoreConsole的配置界面，如图2所示。

CoreConsole项目可在这一点上输出到Libero IDE，同时提供唯一的访问到CoreSPI;或其他IP模块可互连，允许完整的系统从CoreConsole输出到Libero IDE中。

图2：CoreConsole的配置界面六、Actel Libero IDE的输入从CoreConsole的核心产生跟输出后，核心可以被导入到Libero IDE中。

在Libero IDE 中创建新的项目，并从LiberoExport目录导入CoreConsole项目。

Libero IDE将在之后安装核心并且选择测试平台，伴随着制约和相关文件进入到其项目。

注：如果两个或两个以上的DirectCores是必需的，他们可以同时被包含在相同的CoreConsole项目并且在同一时间内输入到Libero IDE中。

七、仿真流程进行仿真，所需的测试平台流程必须选择范围内的CoreConsole，同时保存和生成也必须在“生成”窗格中进行。

通过核心测试平台配置GUI选择所需的测试平台。

两个模拟测试平台支持CoreSPI：1、简单的CoreSPI用户测试平台（VHDL和Verilog）2、完整的CoreSPI验证测试平台（VHDL和Verilog）CoreConsole产生Libero IDE项目时，它会安装相应测试平台的文件。

要运行简单的应用程序或完整的验证环境，在Libero IDE设计层次中简单地设置CoreSPI实例，并单击在Libero IDE设计流程窗口的仿真图标。

这将调用ModelSim®并自动进行仿真。

八、在Actel的Libero IDE中综合适当设置设计程序，点击Libero IDE中的综合图标。

综合窗口出现并显示了Synplicity®项目。

当使用Verilog时要设置以Verilog2001为标准的Synplicity。

要进行综合时，单击Run图标。

九、在Actel的Libero IDE中的布局布线经适当设计的程序设置并进行综合后，点击Libero IDE的布局图标调用Designer。

CoreSPI 不需要特殊的布局布线设置。

（三）接口说明一、参数CoreSPI有参数（Verilog）和泛型（VHDL）来配置RTL代码（如表4）。

所有的参数和泛型都是整数类型。

这些参数或者泛型类型映射在CoreConsole配置窗口中的配置选项中。

表4：CoreSPI参数说明参数值说明系列0到99 必须匹配设置去支持FPGA系列：11-Axcelerator12-RTAX-S14-ProASIC PLUS15-ProASIC316-ProASIC3E17-Fusion20-IGLOO21-IGLOOe使用主模式0，1 如果为1，SPI主逻辑实例化，否则，SPI主逻辑省略使用从模式0，1 如果为1，SPI从逻辑实例化，否则，SPI从逻辑省略在表5和图3中为CoreSPI宏的端口信号定义。

所有信号都指定为“输入”（仅是输入）或“输出”（仅是输出）。

合并后CoreSPI的主模式和从模式有42个I/O信号可以执行。

表5：CoreSPI I/O信号名字类型说明PLCK 输入APB系统时钟；所有内部逻辑的参考时钟。

PRESETN 输入APB低电平有效的异步复位。

PWDATA[7:0] 输入APB写数据。

PADATA[7:0] 输出APB读数据。

PADDR[3:0] 输入APB地址总线。

此端口是用来解决内部CoreSPI寄存器。

PENABLE 输入APB频闪。

指示APB转移的第二个周期。

PSEL 输入APB从模式选择。

选择CoreSPI给APB读写。

PWRITE 输入APB选择读或写信号。

如果为逻辑高电平，APB转移到CoreSPI将进行写数据；如果为逻辑低电平，将从CoreSPI读相关数据。

ENABLE_MASTER 输出主控模式使用静态信号。

如果处于活跃状态，CoreSPI在主模式下运行。

合集下载

spi流程

spi流程

.end= OMAP2_MCSPI3_BASE + 0xff,
.flags= IORESOURCE_MEM,
},
};
static struct platform_device omap2_mcspi3 = {
.name= "omap2_mcspi",
.id= 3,
.num_resources= ARRAY_SIZE(omap2_mcspi3_resources),
.resource= omap2_mcspi3_resources,
.dev= {
.platform_data = &omap2_mcspi3_config,
},
};
static struct omap2_mcspi_platform_config omap2_mcspi4_config = {
.num_cs= 1,
num_chipselect = 2;
break;
#endif
#if defined(CONFIG_ARCH_OMAP3) || defined(CONFIG_ARCH_OMAP4)
case 4:
rxdma_id = spi4_rxdma_id;
txdma_id = spi4_txdma_id;
num_chipselect = 1;
if (r == NULL) {
status = -ENODEV;
goto err1;
}
if (!request_mem_region(r->start, (r->end - r->start) + 1,
dev_name(&pdev->dev))) {
详细设计说明书示例

详细设计说明书示例

1．引言编写目的本说明书提供了freeswan各个模块部件的说明，以供编码人员具体实现及今后的维护工作。

2．总体设计设计原则在确定目标系统的过程中，主要遵循了以下几个原则：目标系统基本上完整地实现IPSec协议族，完全支持VPN的要求；目标系统的服务器端一定要建立在具有自主版权的内核操作系统之上；目标系统的客户端使用方便、界面友好、配置和管理简单灵活。

软件结构该软件由如下几个模块组成：KLIPS模块――实现对进入或外出IP包的安全处理，如：加密、认证等（运行在内核空间）Pluto模块――实现IKE协议，完成安全联盟的协商（运行在用户空间）PF_KEY模块――实现pfkey2协议，完成上述两个模块间关于SA的通信3．程序描述源代码文件组成本程序由两大模块组成，一部分是klips，它运行在操作系统内核空间，主要负责安全联盟和密钥的管理工作，以及对数据报的加密、解密的处理工作；一部分是pluto，它是一个运行在用户空间的守护进程，主要负责安全联盟的协商工作。

下面分别是它们的文件组成：源文件目录|―――freeswan|――klips|――libdes|――pluto|――utilsKLIPS（内核IPsec）详细设计－－―――klips ipsec的核心实现模块|――net|――ipsec|――登记模块，并初始化|――ipsec_tunnel. 数据包的处理并发送模块|――数据包接收并处理模块|――管理SA的模块|――sha1实现模块，由改编|――实现模块|――|――路由表的radix数的实现模块|――对上个文件的改编|――实现PF_KEY2协议的模块|――对上个文件的改编|――|――utils|――用户操作eroute表的模块|――用户操作SA库的模块|――同上|――用户操作虚接口的模块|――登记及初始化模块概要说明功能向内核系统登记几个proc文件，以便于向内核空间中查询安全联盟和eoute表，以及虚接口的状况；初始化SA数据库（tdb链）；初始化SPDB数据库（eroute表）；初始化pf_key（PF_KEY套接口）；模块所涉及的文件: int ipsec_init(void): int ipsec_tdbinit(void): int ipsec_radijinit(void): int pfkey_init(void)变量说明proc文件结构将下列结构登记到内核系统中，则内核就可以通过proc文件系统向应用程序提供一个安全的界面来存取如SA、eroute表等资料。

HB28J128MM3资料

HB28J128MM3资料

HB28K032MM3/HB28K032RM3 HB28L064MM3/HB28L064RM3 HB28J128MM3/HB28J128RM3 HB28J256MM3/HB28J256RM3 HB28J512MM3
MultiMediaCard 32 MByte/64 MByte/128 MByte/256 MByte/512 MByte
1 2 3 4 5 6 7
VCC VPP CS CMD/DI Generator Internal clock OCR[31:0] CID[127:0] CSD[127:0] RCA[15:0] Interface CLK/SCLK DAT/DO Interface driver
CMD
DAT
Flash control
REJ03C0178-0002 Preliminary Rev.0.02 Sep.15.2004
Description
These Renesas MultiMediaCards, HB28K032MM3, HB28K032RM3, HB28L064MM3, HB28L064RM3, HB28J128MM3, HB28J128RM3, HB28J256MM3, HB28J256RM3 and HB28J512MM3 are highly integrated flash memories with serial and random access capability. It is accessible via a dedicated serial interface optimized for fast and reliable data transmission. This interface allows several cards to be stacked by through connecting their peripheral contacts. These Renesas MultiMediaCards are fully compatible to a new consumer standard, called the MultiMediaCard system standard defined in the MultiMediaCard system specification [1]. The MultiMediaCard system is a new mass-storage system based on innovations in semiconductor technology. It has been developed to provide an inexpensive, mechanically robust storage medium in card form for multimedia consumer applications. MultiMediaCard allows the design of inexpensive players and drives without moving parts. A low power consumption and a wide supply voltage range favor mobile, battery-powered applications such as audio players, organizers, palmtops, electronic books, encyclopedia and dictionaries. Using very effective data compression schemes such as MPEG, the MultiMediaCard will deliver enough capacity for all kinds of multimedia data: software/programs, text, music, speech, images, video etc. Notes: 1. MultiMediaCard is a trademark of Infineon Technologies AG. 2. These products are designed and manufactured for retail sale only. Therefore, please contact Renesas Technology's Sales Dept. before using these products in other circumstances. 3. In case that these products are proved to have any defects in manufacturing attributable to Renesas Technology Corp., the defective products can be returned and exchanged for replacements, but Renesas Technology Corp. assumes no responsibility other than exchange. Please contact Renesas Technology's Sales Dept. for further details. Preliminary: The specifications of this device are subject to change without notice. Please contact your nearest Renesas Technology’s Sales Dept. regarding specifications.
esxiwindowscpu多核的设置原理详细说明

esxiwindowscpu多核的设置原理详细说明

esxiwindowscpu多核的设置原理详细说明物理cpu（即插槽）：真实的⼀个CPU；⽐如 2core：⼀个cpu有多少核；⽐如 8hyper threading：超线程技术，即再虚拟个核出来。

所以虚拟软件vmware，esxi最终会算出多少个逻辑cpu：物理cpu(slot) * cores * 2 = 2*8*2=24linux对物理cpu或者slot没有限制。

win10 专业版最多运⾏2个slot或者物理cpu。

在win10上，如果你的esxi虚拟出 vCpu = 16个，由于最多运⾏两个插槽，即2个物理cpu。

那需要配置它的每个cpu核⼼是8核。

这样正好有2 slot。

Setting the Number of Cores per CPU in a Virtual Machine: A How-to GuideWhen creating virtual machines, you should configure processor settings for them. With hardware virtualization, you can select the number of virtual processors for a virtual machine and set the number of sockets and processor cores. How many cores per CPU should you select for optimal performance? Which configuration is better: setting fewer processors with more CPU cores or setting more processors with fewer CPU cores? This blog post explains the main principles of processor configuration for VMware virtual machines. TerminologyFirst of all, let’s go over the definitions of the terms you should know when configuring CPU settings for to help you understand the working principle. Knowing what each term means allows you to avoid confusion about the number of cores per CPU, CPU cores per socket, and the number of CPU cores vs speed.A CPU Socket is a physical connector on the motherboard to which a single physical CPU is connected. A motherboard has at least one CPU socket. Server motherboards usually have multiple CPU sockets that support multiple multicore processors. CPU sockets are standardized for different processor series. Intel and AMD use different CPU sockets for their processor families.A CPU (central processing unit, microprocessor chip, or processor) is a computer component. It is the electronic circuitry with transistors that is connected to a socket. A CPU executes instructions to perform calculations, run applications, and complete tasks. When the clock speed of processors came close to the heat barrier, manufacturers changed the architecture of processors and started producing processors with multiple CPU cores. To avoid confusion between physical processors and logical processors or processor cores, some vendors refer to a physical processor as a socket.A CPU core is the part of a processor containing the L1 cache. The CPU core performs computational tasks independently without interacting with other cores and external components of a “big” processor that are shared among cores. Basically, a core can be considered as a small processor built into the main processor that is connected to a socket. Applications should support parallel computations to use multicore processors rationally.Hyper-threading is a technology developed by Intel engineers to bring parallel computation to processors that have one processor core. The debut of hyper-threading was in 2002 when the Pentium 4 HT processor was released and positioned for desktop computers. An operating system detects a single-core processor with hyper-threading as a processor with two logical cores (not physical cores). Similarly, a four-core processor with hyper-threading appears to an OS as a processor with 8 cores. The more threads run on each core, the more tasks can be done in parallel. Modern Intel processors have both multiple cores and hyper-threading. Hyper-threading is usually enabled by default and can be enabled or disabled in BIOS. AMD simultaneous multi-threading (SMT) is the analog of hyper-threading for AMD processors.A vCPU is a virtual processor that is configured as a virtual device in the virtual hardware settings of a VM. A virtual processor can be configured to use multiple CPU cores. A vCPU is connected to a virtual socket.CPU overcommitment is the situation when you provision more logical processors (CPU cores) of a physical host to VMs residing on the host than the total number of logical processors on the host.NUMA (non-uniform memory access) is a computer memory design used in multiprocessor computers. The idea is to provide separate memory for each processor (unlike UMA, where all processors access shared memory through a bus). At the same time, a processor can access memory that belongs to other processors by using a shared bus (all processors access all memory on the computer). A CPU has a performance advantage of accessing own local memory faster than other memory on a multiprocessor computer.These basic architectures are mixed in modern multiprocessor computers. Processors are grouped on a multicore CPU package or node. Processors that belong to the same node share access to memory modules as with the UMA architecture. Also, processors can access memory from the remote node via a shared interconnect. Processors do so for the NUMA architecture but with slower performance. This memory access is performed through the CPU that owns that memory rather than directly.NUMA nodes are CPU/Memory couples that consist of a CPU socket and the closest memory modules. NUMA is usually configured in BIOS as the node interleaving or interleaved memory setting.An example. An ESXi host has two sockets (two CPUs) and 256 GB of RAM. Each CPU has 6 processor cores. This server contains two NUMA nodes. Each NUMA node has 1 CPU socket (one CPU), 6 Cores, and 128 GB of RAM.always tries to allocate memory for a VM from a native (home) NUMA node. A home node can be changed automatically if there are changes in VM loads and ESXi server loads.Virtual NUMA (vNUMA) is the analog of NUMA for VMware virtual machines. A vNUMA consumes hardware resources of more than one physical NUMA node to provide optimal performance. The vNUMA technology exposes the NUMA topology to a guest operating system. As a result, the guest OS is aware of the underlying NUMA topology for the most efficient use. The virtual hardware version of a VM must be 8 or higher to use vNUMA. Handling of vNUMA was significantly improved in VMware vSphere 6.5, and this feature is no longer controlled by the CPU cores per socket value in the VM configuration. By default, vNUMA is enabled for VMs that have more than 8 logical processors (vCPUs). You can enable vNUMA manually for a VM by editing the VMX configuration file of the VM and adding theline numa.vcpu.min=X, where X is the number of vCPUs for the virtual machine.CalculationsLet’s find out how to calculate the number of physical CPU cores, logical CPU cores, and other parameters on a server.The total number of physical CPU cores on a host machine is calculated with the formula:(The number of Processor Sockets) x (The number of cores/processor) = The number of physical processor cores*Processor sockets only with installed processors must be considered.If hyper-threading is supported, calculate the number of logical processor cores by using the formula:(The number of physical processor cores) x (2 threads/physical processor) = the number of logical processorsFinally, use a single formula to calculate available processor resources that can be assigned to VMs:(CPU sockets) x (CPU cores) x (threads)For example, if you have a server with two processors with each having 4 cores and supporting hyper-threading, then the total number of logical processors that can be assigned to VMs is2(CPUs) x 4(cores) x 2(HT) = 16 logical processorsOne logical processor can be assigned as one processor or one CPU core for a VM in VM settings.As for virtual machines, due to hardware emulation features, they can use multiple processors and CPU cores in their configuration for operation. One physical CPU core can be configured as a virtual CPU or a virtual CPU core for a VM.The total amount of clock cycles available for a VM is calculated as:(The number of logical sockets) x (The clock speed of the CPU)For example, if you configure a VM to use 2 vCPUs with 2 cores when you have a physical processor whose clock speed is 3.0 GHz, then the total clock speed is 2x2x3=12 GHz. If CPU overcommitment is used on an ESXi host, the available frequency for a VM can be less than calculated if VMs perform CPU-intensive tasks.LimitationsThe maximum number of virtual processor sockets assigned to a VM is 128. If you want to assign more than 128 virtual processors, configure a VM to use multicore processors.The maximum number of processor cores that can be assigned to a single VM is 768 in vSphere 7.0 Update 1. A virtual machine cannot use more CPU cores than the number of logical processor cores on a physical machine.CPU hot add. If a VM has 128 vCPUs or less than 128 vCPUs, then you cannot use the CPU hot add feature for this VM and edit the CPU configuration of a VM while a VM is in the running state.OS CPU restrictions. If an operating system has a limit on the number of processors, and you assign more virtual processors for a VM, the additional processors are not identified and used by a guest OS. Limits can be caused by OS technical design and OS licensing restrictions. Note that there are operating systems that are licensed per-socket and per CPU core (for example, ).CPU support limits for some operating systems:Windows 10 Pro – 2 CPUsWindows 10 Home – 1 CPUWindows 10 Workstation – 4 CPUsWindows Server 2019 Standard/Datacenter – 64 CPUsWindows XP Pro x64 – 2 CPUsWindows 7 Pro/Ultimate/Enterprise - 2 CPUsWindows Server 2003 Datacenter – 64 CPUsConfiguration RecommendationsFor older vSphere versions, I recommend using sockets over cores in VM configuration. At first, you might not see a significant difference in CPU sockets or CPU cores in VM configuration for VM performance. Be aware of some configuration features. Remember about NUMA and vNUMA when you consider setting multiple virtual processors (sockets) for a VM to have optimal performance.If vNUMA is not configured automatically, mirror the NUMA topology of a physical server. Here are some recommendations for VMs in VMware vSphere 6.5 and later:When you define the number of logical processors (vCPUs) for a VM, prefer the cores-per-socket configuration. Continue until the count exceeds the number of CPU cores on a single NUMA node on the ESXi server. Use the same logic until you exceed the amount of memory that is available on a single NUMA node of your physical ESXi server.Sometimes, the number of logical processors for your VM configuration is more than the number of physical CPU cores on a single NUMA node, or the amount of RAM is higher than the total amount of memory available for a single NUMA node. Consider dividing the count of logical processors (vCPUs) across the minimum number of NUMA nodes for optimal performance.Don’t set an odd number of vCPUs if the CPU count or amount of memory exceeds the number of CPU cores. The same applies in case memory exceeds the amount of memory for a single NUMA node on a physical server.Don’t create a VM that has a number of vCPUs larger than the count of physical processor cores on your physical host.If you cannot disable vNUMA due to your requirements, don’t enable the vCPU Hot-Add feature.If vNUMA is enabled in vSphere prior to version 6.5, and you have defined the number of logical processors (vCPUs) for a VM, select the number of virtual sockets for a VM while keeping the cores-per-socket amount equal to 1 (that is the default value). This is because the one-core-per-socket configuration enables vNUMA to select the best vNUMA topology to the guest OS automatically. This automatic configuration is optimal on the underlying physical topology of the server. If vNUMA is enabled, and you’re using the same number of logical processors (vCPUs) but increase the number of virtual CPU cores and reduce the number of virtual sockets by the same amount, then vNUMA cannot set the best NUMA configuration for a VM. As a result, VM performance is affected and can degrade.If a guest operating system and other software installed on a VM are licensed on a per-processor basis, configure a VM to use fewer processors with more CPU cores. For example, Windows Server 2012 R2 is licensed per socket, and Windows Server 2016 is licensed on a per-core basis.If you use CPU overcommitment in the configuration of your VMware virtual machines, keep in mind these values: 1:1 to 3:1 – There should be no problems in running VMs3:1 to 5:1 – Performance degradation is observed6:1 – Prepare for problems caused by significant performance degradationCPU overcommitment with normal values can be used in test and dev environments without risks.Configuration of VMs on ESXi HostsFirst of all, determine how many logical processors (Total number of CPUs) of your physical host are needed for a virtual machine for proper work with sufficient performance. Then define how many virtual sockets with processors (Number of Sockets in vSphere Client) and how many CPU cores (Cores per Socket) you should set for a VM keeping in mind previous recommendations and limitations. The table below can help you select the needed configuration.If you need to assign more than 8 logical processors for a VM, the logic remains the same. To calculate the number of logical CPUs in , multiply the number of sockets by the number of cores. For example, if you need to configure a VM to use 2-processor sockets, each has 2 CPU cores, then the total number of logical CPUs is 2*2=4. It means that you should select 4 CPUs in the virtual hardware options of the VM in vSphere Client to apply this configuration.Let me explain how to configure CPU options for a VM in VMware vSphere Client. Enter the IP address of your in a web browser, and open VMware vSphere Client. In the navigator, open Hosts and Clusters, and select the needed virtual machine that you want to configure. Make sure that the VM is powered off to be able to change CPU configuration.Right-click the VM, and in the context menu, hit Edit Settings to open virtual machine settings.Expand the CPU section in the Virtual Hardware tab of the Edit Settings window.CPU. Click the drop-down menu in the CPU string, and select the total number of needed logical processors for this VM. In this example, Iselect 4 logical processors for the Ubuntu VM (blog-Ubuntu1).Cores per Socket. In this string, click the drop-down menu, and select the needed number of cores for each virtual socket (processor). CPU Hot Plug. If you want to use this feature, select the Enable CPU Hot Add checkbox. Remember limitations and requirements. Reservation. Select the guaranteed minimum allocation of CPU clock speed (frequency, MHz, or GHz) for a virtual machine on an ESXi host or cluster.Limit. Select the maximum CPU clock speed for a VM processor. This frequency is the maximum frequency for a virtual machine, even if this VM is the only VM running on the ESXi host or cluster with more free processor resources. The set limit is true for all virtual processors of a VM. If a VM has 2 single-core processors, and the limit is 1000 MHz, then both virtual processors work with a total clock speed of one million cycles per second (500 MHz for each core).Shares. This parameter defines the priority of resource consumption by virtual machines (Low, Normal, High, Custom) on an ESXi host or resource pool. Unlike Reservation and Limit parameters, the Shares parameter is applied for a VM only if there is a lack of CPU resources within an ESXi host, resource pool, or DRS cluster.Available options for the Shares parameter:Low – 500 shares per a virtual processorNormal - 1000 shares per a virtual processorHigh - 2000 shares per a virtual processorCustom – set a custom valueThe higher the Shares value is, the higher the amount of CPU resources provisioned for a VM within an ESXi host or a resource pool. Hardware virtualization. Select this checkbox to enable . This option is useful if you want to run a VM inside a VM for testing or educational purposes.Performance counters. This feature is used to allow an application installed within the virtual machine to be debugged and optimized after measuring CPU performance.Scheduling Affinity. This option is used to assign a VM to a specific processor. The entered value can be like this: “0, 2, 4-7”.I/O MMU. This feature allows VMs to have direct access to hardware input/output devices such as storage controllers, network cards, graphic cards (rather than using emulated or paravirtualized devices). I/O MMU is also called Intel Virtualization Technology for Directed I/O (Intel VT-d) and AMD I/O Virtualization (AMD-V). I/O MMU is disabled by default. Using this option is deprecated in vSphere 7.0. If I/O MMU is enabled for a VM, the VM cannot be migrated with and is not compatible with snapshots, memory overcommit, suspended VM state, physical NIC sharing, and .If you use a standalone ESXi host and use VMware Host Client to configure VMs in a web browser, the configuration principle is the same as for VMware vSphere Client.If you connect to vCenter Server or ESXi host in and open VM settings of a vSphere VM, you can edit the basic configuration of virtual processors. Click VM > Settings, select the Hardware tab, and click Processors. On the following screenshot, you see processor configuration for the same Ubuntu VM that was configured before in vSphere Client. In the graphical user interface (GUI) of VMware Workstation, you should select the number of virtual processors (sockets) and the number of cores per processor. The number of total processor cores (logical cores of physical processors on an ESXi host or cluster) is calculated and displayed below automatically. In the interface of vSphere Client, you set the number of total processor cores (the CPUs option), select the number of cores per processor, and then the number of virtual sockets is calculated and displayed.Configuring VM Processors in PowerCLIIf you prefer using the command-line interface to configure components of VMware vSphere, use to edit the CPU configuration of VMs. Let’s find out how to edit VM CPU configuration for a VM which name is Ubuntu 19 in Power CLI. The commands are used for VMs that are powered off.To configure a VM to use two single-core virtual processors (two virtual sockets are used), use the command:get-VM -name Ubuntu19 | set-VM -NumCpu 2Enter another number if you want to set another number of processors (sockets) to a VM.In the following example, you see how to configure a VM to use two dual-core virtual processors (2 sockets are used):$VM=Get-VM -Name Ubuntu19$VMSpec=New-Object -Type VMware.Vim.VirtualMachineConfigSpec -Property @{ "NumCoresPerSocket" = 2}$VM.ExtensionData.ReconfigVM_Task($VMSpec)$VM | Set-VM -NumCPU 2Once a new CPU configuration is applied to the virtual machine, this configuration is saved in the VMX configuration file of the VM. In my case, I check the Ubuntu19.vmx file located in the VM directory on the datastore (/vmfs/volumes/datastore2/Ubuntu19/). Lines with new CPU configuration are located at the end of the VMX file.numvcpus = "2"cpuid.coresPerSocket = "2"If you need to reduce the number of processors (sockets) for a VM, use the same command as shown before with less quantity. For example, to set one processor (socket) for a VM, use this command:get-VM -name Ubuntu19 | set-VM -NumCpu 1The main advantage of using Power CLI is the ability to configure multiple VMs in bulk. is important and convenient if the number of virtual machines to configure is high. Use VMware cmdlets and syntax of Microsoft PowerShell to create scripts.ConclusionThis blog post has covered the configuration of virtual processors for VMware vSphere VMs. Virtual processors for virtual machines are configured in VMware vSphere Client and in Power CLI. The performance of applications running on a VM depends on the correct CPU and memory configuration. In VMware vSphere 6.5 and later versions, set more cores in CPU for virtual machines and use the CPU cores per socket approach. If you use vSphere versions older than vSphere 6.5, configure the number of sockets without increasing the number of CPU cores for a VM due to different behavior of vNUMA in newer and older vSphere versions. Take into account the licensing model of software you need to install on a VM. If the software is licensed on using a per CPU model, configure more cores per CPU in VM settings. When using virtual machines in VMware vSphere, don’t forget about . Use NAKIVO Backup & Replication to back up your virtual machines, including VMs that have multiple cores per CPU. Regular backup helps you protect your data and recover the data in case of a .5(100%)4votes。