support for the directive, which does not explain-no-mmx ....... Compile with use of MMX instructions+-mmx ...... ..... Compile with use of MMX instructions-no-3dnow ..... Do not compileWith use of 3DNOW instructions+ -3dnow ....... Compile with use of 3DNOW instructions-no-sse ....... Don't compile with use of SSE in
put_task_struct_delayed (), mmdrop_delayed () manages mmdrop () by queue.* The tif_need_resched_delayed flag can be used for rescheduling, but the scheduling will be delayed until the process is ready to return to the user space,Or the next preempt_check_resched_delayed (). The key point of both is to avoid unnecessary preemption (high-priority tasks that will be awakenedWill wait for the current task to release a lock ). If the tif_need_resched_delayed flag is not specifiedImmediately preempti
Sometimes you need to collect various information about the server, such as CPU information, memory information, Linux version information, and various software information installed. The following describes how to view the main indicators. 1. view the Linux release information [root @ pcmweb ~] # Cat/etc/issue
Red Hat Enterprise Linux Server Release 5 (tikanga)
Kernel on an m2. view Linux kernel information [root @ pcmweb ~] # Uname-R
2.6.18-8. el5xen3. View CPU information [root @ pcmxexdb ~]
-rtti ...... do not compile the runtime type information.
*-Rtti ............. indicates the type of the compilation runtime.
// The following statements are supported.
-No-MMX ...... do not compile with use of MMX instructions
+-MMX .......... compile with use of MMX instructions
-No-3dnow ...... do not compile
With u
64bit)7. View CPU Information Summary[Email protected] tomcat6]$lscpuARCHITECTURE:X86_64 #CPU Op-mode (s): 32-bit, 64-bitByte Order:little EndianCPU (s): 4On-line CPU (s) list:0-3Thread (s) per core:1Core (s) per Socket:2Socket (s): 2NUMA node (s): 1Vendor Id:genuineintelCPU Family:6Model:44Stepping:2CPU mhz:2533.423bogomips:5066.84Hypervisor Vendor:vmwareVirtualization Type:fullL1D cache:32kL1i cache:32kL2 cache:256kL3 cache:12288kNUMA node0 CPU (s): 0-38. View CPU Information Summary (compare
Take the CentOS system as an exampleFirst, the CPUCat/proc/cpuinfoHere is my CPU information, with 4 messages stating there are 4 logical CPUs, but each physical ID is the same, stating that there are only 1 physical CPUs.1. The "Physical ID" and "core ID" of multiple logical CPUs are the same, indicating that hyper-threading is turned on.2. There is an LM tag in the flags stating that it is a 64-bit CPU3, my processor has 4 different numbers, and belong to a physical ID, while the CPU cores val
called by the system, the Ring3 enters Ring0, which wastes a lot of CPU cycles, for example, system calls must be directed from Ring3 to Ring0 (except for the INT command called by the kernel, most of which are performed by the Hacker kernel module). The level before and after permission escalation is fixed, CPL must be 3, and the DPL of INT 80 must be 3, so that the CPU checks the DPL of the gate Descriptor and the CPL of the caller is completely unnecessary. Because of this, Intel x86 CPU sta
bath2009.02.25 guide to Western Classical Music Appreciation2009.02.25 guide to Driver Design for Windows NT Devices2009.02.25 C # function utility Manual2009.04.07 C # Advanced Programming2009.04.07 introduction to roboticsOperating System 2009.04.072009.04.07 Linux programming Essence2009.05.05 dos secrets2009.05.05 spring and autumn in ten countries. Volume 1 to Volume 32009.05.11 intel series microprocessor architecture and programming interface title: The intel microprocessors: 8086/8088,
Typical Pentium software delay loops can be written using mov and loop instructions.For example, the following instruction sequence can be used for a delay loop: mov CX, countdelay: loop delayThe initial loop counter value of "Count" can be calculated using the cycles required to execute the following Pentium instructions: mov REG/Imm (1 cycle) loop label (5/6 cycles)Note that the
.//////////////////////////////////////// //////////////////////////////////////// ///////////////////////////
{
Large_integer privious, current, elapse;
Queryperformancecounter ( privious );
Current = privious;
While (current. quadpart-privious. quadpart
Queryperformancecounter (counter t );
Elapse. quadpart = current. quadpart-privious. quadpart;
Return elapse;
}
Note: Do not forget to add a function declaration for this function in the header file.
Now, you can compile and execute this proje
(large_integer interval)
//////////////////////////////////////// //////////////////////////////////////// /////////////////////////////
// Function: perform the actual latency Function
// Parameter: The interval parameter is the number of time-related delays to be executed.
// Return value: returns the number of time-related values after the function is executed.
//////////////////////////////////////// //////////////////////////////////////// ///////////////////////////
{
Large_integer privio
.//////////////////////////////////////// //////////////////////////////////////// ///////////////////////////
{
Large_integer privious, current, elapse;
Queryperformancecounter ( privious );
Current = privious;
While (current. quadpart-privious. quadpart
Queryperformancecounter (counter t );
Elapse. quadpart = current. quadpart-privious. quadpart;
Return elapse;
}
Note: Do not forget to add a function declaration for this function in the header file.
Now, you can compile and execute this
is very little chance of such a situation. Maybe some VB programmers have never met it, but it does exist.
There are several options in the local code:
A) code Speed Optimization: This option can compile execution files that are faster, but the execution files are relatively large. Recommended
B) Code Size Optimization: This option can compile a relatively small execution file, but it is not recommended at the cost of speed.
C) No optimization: This option only converts the p-code to the
solved this problem by adding the DoEvent statement to the code. Of course, there is very little chance of such a situation. Maybe some VB programmers have never met it, but it does exist.
There are several options in the local code:
A) code Speed Optimization: This option can compile execution files that are faster, but the execution files are relatively large. Recommended
B) Code Size Optimization: This option can compile a relatively small execution file, but it is not recommended at the cos
execution files that are faster, but the execution files are relatively large. Recommended
B) Code Size Optimization: This option can compile a relatively small execution file, but it is not recommended at the cost of speed.
C) No optimization: This option only converts the P-code to the local code without any optimization. It can be used when debugging code.
D) Optimization for Pentium Pro: although this option is not the default option in the lo
processor generates a special bus cycle to indicate the Enter stop mode. The hardware responds to this signal in several ways. The indicator light on the front panel lights up, generating an NMI interrupt to record diagnostic information, calling the reset initialization process (note that the binit# pin was introduced in the Pentium Pro processor). If non-wake events (such as a20m# interrupts) are not processed during the outage, they are processed
operation of the memory is performed atomically. In processors prior to Pentium and Pentium, instructions with a lock prefix lock the bus during execution, leaving other processors temporarily unable to access memory through the bus. Obviously, this will cost you dearly. Starting with the Pentium 4,intel Xeon and P6 processors, Intel has made a significant optim
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.