Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

openssl_ia32cap(3) [centos man page]

OPENSSL_ia32cap(3)						      OpenSSL							OPENSSL_ia32cap(3)

NAME
OPENSSL_ia32cap - finding the IA-32 processor capabilities SYNOPSIS
unsigned long *OPENSSL_ia32cap_loc(void); #define OPENSSL_ia32cap (*(OPENSSL_ia32cap_loc())) DESCRIPTION
Value returned by OPENSSL_ia32cap_loc() is address of a variable containing IA-32 processor capabilities bit vector as it appears in EDX register after executing CPUID instruction with EAX=1 input value (see Intel Application Note #241618). Naturally it's meaningful on IA-32[E] platforms only. The variable is normally set up automatically upon toolkit initialization, but can be manipulated afterwards to modify crypto library behaviour. For the moment of this writing six bits are significant, namely: 1. bit #28 denoting Hyperthreading, which is used to distiguish cores with shared cache; 2. bit #26 denoting SSE2 support; 3. bit #25 denoting SSE support; 4. bit #23 denoting MMX support; 5. bit #20, reserved by Intel, is used to choose between RC4 code pathes; 6. bit #4 denoting presence of Time-Stamp Counter. For example, clearing bit #26 at run-time disables high-performance SSE2 code present in the crypto library. You might have to do this if target OpenSSL application is executed on SSE2 capable CPU, but under control of OS which does not support SSE2 extentions. Even though you can manipulate the value programmatically, you most likely will find it more appropriate to set up an environment variable with the same name prior starting target application, e.g. on Intel P4 processor 'env OPENSSL_ia32cap=0x12900010 apps/openssl', to achieve same effect without modifying the application source code. Alternatively you can reconfigure the toolkit with no-sse2 option and recompile. 1.0.1e 2013-02-11 OPENSSL_ia32cap(3)

Check Out this Related Man Page

OPENSSL_ia32cap(3)						      OpenSSL							OPENSSL_ia32cap(3)

NAME
OPENSSL_ia32cap - finding the IA-32 processor capabilities LIBRARY
libcrypto, -lcrypto SYNOPSIS
unsigned long *OPENSSL_ia32cap_loc(void); #define OPENSSL_ia32cap (*(OPENSSL_ia32cap_loc())) DESCRIPTION
Value returned by OPENSSL_ia32cap_loc() is address of a variable containing IA-32 processor capabilities bit vector as it appears in EDX register after executing CPUID instruction with EAX=1 input value (see Intel Application Note #241618). Naturally it's meaningful on IA-32[E] platforms only. The variable is normally set up automatically upon toolkit initialization, but can be manipulated afterwards to modify crypto library behaviour. For the moment of this writing six bits are significant, namely: 1. bit #28 denoting Hyperthreading, which is used to distiguish cores with shared cache; 2. bit #26 denoting SSE2 support; 3. bit #25 denoting SSE support; 4. bit #23 denoting MMX support; 5. bit #20, reserved by Intel, is used to choose between RC4 code pathes; 6. bit #4 denoting presence of Time-Stamp Counter. For example, clearing bit #26 at run-time disables high-performance SSE2 code present in the crypto library. You might have to do this if target OpenSSL application is executed on SSE2 capable CPU, but under control of OS which does not support SSE2 extentions. Even though you can manipulate the value programmatically, you most likely will find it more appropriate to set up an environment variable with the same name prior starting target application, e.g. on Intel P4 processor 'env OPENSSL_ia32cap=0x12900010 apps/openssl', to achieve same effect without modifying the application source code. Alternatively you can reconfigure the toolkit with no-sse2 option and recompile. 1.0.1i 2011-06-05 OPENSSL_ia32cap(3)
Man Page

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

hp-ux

hi, I have got a simple doubt, How to find whether i am working on 32 bit hp-ux or 64 bit hp-ux? is their any system call by which i can print it in my 'c ' code. Thanx in advance. (2 Replies)
Discussion started by: sushaga
2 Replies

2. Programming

Troubles with HPUX

Hello I created an application in c language for HP-UX operative system,and it runs on a 32 bits PARISC processor. My problem is that I have to run this same application but now in a 64 bits Parisc processor. But I am not able to compile the application with the 64 bit server, and I only could use... (1 Reply)
Discussion started by: masterboy6666
1 Replies

3. UNIX for Advanced & Expert Users

distinguishing between 32 bit and 64 bit OS's

I have a C application which is to be supported on AIX, Solaris and HPUX. There are chunks of code which need to #ifdef'd for 64 bit OS's only, i.e., I need these code to be executed only for 64 bit OS's on all the three platforms. Can someone guide me how to do this. I tried using #ifdef _LP64... (0 Replies)
Discussion started by: hirandhir
0 Replies

4. AIX

regd 32-bit and 64 bit programming models

i read that an application can remain as a 32-bit applicarion and still run on a 64-bit operating system without any code changes. But some documents also suggest that during porting 32 bit applications need to have code changes especially pointers and int and long and that they should be... (2 Replies)
Discussion started by: TECHRAMESH
2 Replies

5. Linux

Is it possible to compile 64 bit application on 32 bit machine

Hi, I am using 32 bit machine, and I want to compile 64 bit application on 32-bit machine. So please tell me is it possible or not? Regards Mandar (7 Replies)
Discussion started by: Mandar123
7 Replies

6. SCO

Speedstep/Hyperthread with SCO

Hello, I am running SCO Operserver 5.0.7 on a computer that has a Intel Duo core processor. The BIOS supports Intel Speedstep which is similar to Intel Hyperthreading and it is enabled. In the boot file I added ENABLE_HT=Y ENABLE_JT=Y HYPERTHREAD=Y and in the space.c file I added ... (1 Reply)
Discussion started by: ewerezak
1 Replies

Featured Tech Videos