Sponsored Content
Full Discussion: Intel vs. RISC
Top Forums UNIX for Dummies Questions & Answers Intel vs. RISC Post 2085 by softarch on Wednesday 18th of April 2001 10:47:54 AM
Old 04-18-2001
Power

I have to admit. When we got the “Sun Ultra 5 Ultrasparc Driven” workstation, 400MHz, 20Gb drive, I asked my boss if should get Intel with Unix on it. But it is for the clients to show we have real “SPARK”. Since then I adjusted and now I somehow do not mind its slow performance. I am Java developer and so performance is very crucial to me. Not too many managers understand that. gp
 

8 More Discussions You Might Find Interesting

1. AIX

Ibm Risc/6000 Os

:o Unix Sirs, :eek:RE: IBM RISC/6000 1990 Used on Application: Image buffer: 3D "Catia" (3D "Autocad" sim.) engineering C.A.D. Written by Deso. Cash prior to main frame dump:cool: * :oCan I purchase the oem operating system from you unix people? :cool: ... (1 Reply)
Discussion started by: penguins
1 Replies

2. HP-UX

please help need HP-UX 11 for PA RISC

Im not asking for an illegal copy (but from what i understand if i have the system its not illegal to give it to me) just how to get a copy of hp-ux period i have some old hp visualize systems based on the PA8500 400mhz cpu spent days on the phone with hp they no nothing and there website is a... (6 Replies)
Discussion started by: maliqua
6 Replies

3. HP-UX

Debian HPPA for HP PA-RISC

Hi, I just downloaded the debian HPPA distribution. Once I try to install it on my C3000 box, the machine boots, reads a part of the CD but then stalls with an error message about the image on the CD. The CD drive is IDE, maybe debian expects to have a SCSI one. Somebody already tried to... (1 Reply)
Discussion started by: ddegrendele
1 Replies

4. UNIX for Advanced & Expert Users

PA-RISC 2.0 (LP64) and PA-RISC2.0 exec or libraries

I have a problem with executing an application using the ELF 64 libraries. Previous versions and on other machines where all is well use PA-RISC2.0 (32) . My guess is that the application or executables need to be recompiled and linked with the new ELF 64 libraries. Are these run time compatible ?... (2 Replies)
Discussion started by: gd2352
2 Replies

5. HP-UX

HP-UX 11i v2 for PA-RISC

Hello, i trying to get HP-UX 11i v2 for PA-RISC. I`im to poor to buy this system, so I`am asking that someone can help me. best regards email removed (1 Reply)
Discussion started by: mruczas
1 Replies

6. Programming

IBM Risc migration

Hi all, I have been dealing with the following problem one week now without any progress. I've a source code written in C which is using X libraries in order to create a graphical interface to visualise results produced by another code written in Fortran. The README file of the C code says... (2 Replies)
Discussion started by: Pavlos
2 Replies

7. HP-UX

Access AS400 from HP (RISC) Unix OS

Hi everyone, I am in the need of some software which will allow me to access IBM AS400 from HP unix operating system. I could download the software from IBM site for windows OS and it is working succesfully. I need to do the same on UNIX OS. Could you please guide me to some site... (1 Reply)
Discussion started by: vkoppula
1 Replies

8. HP-UX

Does HP-UX On Itanium always come with PA-RISC compatibility

Does anybody know if HP-UX on Itanium always comes with backwards compatibility for PA-RISC applications? I've heard that there is an emulator called Aries which should do the trick, I just need to know if it always comes as standard with HP-UX Itanium systems. Any help would be greatly... (3 Replies)
Discussion started by: nialler
3 Replies
cpc_npic(3CPC)					    CPU Performance Counters Library Functions					    cpc_npic(3CPC)

NAME
cpc_npic, cpc_caps, cpc_cciname, cpc_cpuref, cpc_walk_events_all, cpc_walk_events_pic, cpc_walk_attrs - determine CPU performance counter configuration SYNOPSIS
cc [ flag... ] file... -lcpc [ library... ] #include <libcpc.h> const char *cpc_cciname(cpc_t *cpc); const char *cpc_cpuref(cpc_t *cpc); uint_t cpc_npic(cpc_t *cpc); uint_t cpc_caps(cpc_t *cpc); void cpc_walk_events_all(cpc_t *cpc, void *arg, void (*action)(void *arg, const char *event)); void cpc_walk_events_pic(cpc_t *cpc, uint_t picno, void *arg, void (*action)(void *arg, uint_t picno, const char *event)); void cpc_walk_attrs(cpc_t *cpc, void *arg, void (*action)(void *arg, const char *attr)); DESCRIPTION
The cpc_cciname() function returns a printable description of the processor performance counter interfaces, for example, the string Ultra- SPARC III+ & IV. This name should not be assumed to be the same as the name the manufacturer might otherwise ascribe to the processor. It simply names the performance counter interfaces as understood by the system, and thus names the set of performance counter events that can be described by that interface. The cpc_cpuref() function returns a string that describes a reference work that should be consulted to (allow a human to) understand the semantics of the performance counter events that are known to the system. The string returned might be substantially longer than 80 charac- ters. Callers printing to a terminal might want to insert line breaks as appropriate. The cpc_npic() function returns the number of performance counters accessible on the processor. The cpc_caps() function returns a bitmap containing the bitwise inclusive-OR of zero or more flags that describe the capabilities of the processor. If CPC_CAP_OVERFLOW_INTERRUPT is present, the processor can generate an interrupt when a hardware performance counter overflows. If CPC_CAP_OVERFLOW_PRECISE is present, the processor can determine precisely which counter overflowed, thereby affecting the behavior of the overflow notification mechanism described in cpc_bind_curlwp(3CPC). The system maintains a list of performance counter events supported by the underlying processor. Some processors are able to count all events on all hardware counters, while other processors restrict certain events to be counted only on specific hardware counters. The sys- tem also maintains a list of processor-specific attributes that can be used for advanced configuration of the performance counter hardware. These functions allow applications to determine what events and attributes are supported by the underlying processor. The reference work pointed to by cpc_cpuref() should be consulted to understand the reasons for and use of the attributes. The cpc_walk_events_all() function calls the action function on each element of a global event list. The action function is called with each event supported by the processor, regardless of which counter is capable of counting it. The action function is called only once for each event, even if that event can be counted on more than one counter. The cpc_walk_events_pic() function calls the action function with each event supported by the counter indicated by the picno argument, where picno ranges from 0 to the value returned by cpc_npic(). The system maintains a list of attributes that can be used to enable advanced features of the performance counters on the underlying pro- cessor. The cpc_walk_attrs() function calls the action function for each supported attribute name. See the reference material as returned by cpc_cpuref(3CPC) for the semantics use of attributes. RETURN VALUES
The cpc_cciname() function always returns a printable description of the processor performance counter interfaces. The cpc_cpuref() function always returns a string that describes a reference work. The cpc_npic() function always returns the number of performance counters accessible on the processor. The cpc_caps() function always returns a bitmap containing the bitwise inclusive-OR of zero or more flags that describe the capabilities of the processor. If the user-defined function specified by action is not called, the cpc_walk_events_all(), cpc_walk_events_pic(), and cpc_walk_attrs() functions set errno to indicate the error. ERRORS
The cpc_walk_events_all(), cpc_walk_events_pic(), and cpc_walk_attrs() functions will fail if: ENOMEM There is not enough memory available. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ |MT-Level |Safe | +-----------------------------+-----------------------------+ SEE ALSO
cpc_bind_curlwp(3CPC), libcpc(3LIB), attributes(5) SunOS 5.10 30 Jan 2004 cpc_npic(3CPC)
All times are GMT -4. The time now is 01:08 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy